topic Re: Velocity - Update Attribute on Existing Record? in ArcGIS Velocity Questions

Velocity - Update Attribute on Existing Record?

ArthurSmith2 — Mon, 23 Feb 2026 17:17:54 GMT

Hello All! I am looking for ideas and suggestions to build a Velocity Analytic that updates an attribute column on an existing record in a ArcGIS Online Hosted Feature Layer.

I set up a http receiver feed that ingests delimited data with a record ID that matches ID in my hosted feature layer and want to update a column to 'Yes' anytime a matching record received from this feed; please see Analytic screenshot below. This Analytic is not doing anything currently; the record remains unchanged.

Functionality I am looking for is similar to this tool in GeoEvent Server: Update a Feature—ArcGIS GeoEvent Server Help | Documentation for ArcGIS Enterprise

Let me know if anyone has ideas!

Re: Velocity - Update Attribute on Existing Record?

JeffSilberberg — Mon, 23 Feb 2026 21:52:12 GMT

See this post ==

https://community.esri.com/t5/arcgis-velocity-questions/translate-a-sql-update-to-a-velocity-output/m-p/1572703#M490

Re: Velocity - Update Attribute on Existing Record?

ArthurSmith2 — Mon, 23 Feb 2026 22:54:50 GMT

Thanks @JeffSilberberg!

Were you ever able to get this implemented on your end? I did some testing here, and am unable to get the field mapping to work out. The static layer I bring in to get all the fields that are not being updated doesn't appear to transfer through after the Join Fields.

Re: Velocity - Update Attribute on Existing Record?

JeffSilberberg — Tue, 24 Feb 2026 03:31:11 GMT

Yes, worked great.

Do you have a Track_id on the Feature Layer, and be sure that the output from the "Map Fields" specifies the same Track_id, or use "Select Fields" to limit the number of fields you are passing to the "Feature Layer".

Re: Velocity - Update Attribute on Existing Record?

ArthurSmith2 — Tue, 24 Feb 2026 16:15:51 GMT

I believe the Track ID is the issue... the existing output feature layer was created outside of Velocity, so has no Track ID defined.

A little backstory on our process: the existing feature layer we want to update a single column on via Velocity is a permit info layer that is created and maintained by Survey123 and other web apps, integrated with Power Automate and has 300+ fields. It would be impractical to rebuild this as a Velocity-managed layer.

Going to keep investigating... but think this may be impossible unless the layer was created/is managed by Velocity.

@JeffSilberberg in your case, was the existing feature layer you update Velocity-managed?

Re: Velocity - Update Attribute on Existing Record?

JeffSilberberg — Tue, 24 Feb 2026 16:22:21 GMT

@JeffSilberberg in your case, was the existing feature layer you update Velocity-managed?

Yes, it's a Last Known Location for devices reporting -- and in some cases, we update a report Reason and Time only, as the Time to First Lock can mean we get reports with no location information.

Re: Velocity - Update Attribute on Existing Record?

Jeff_G — Tue, 24 Feb 2026 17:46:30 GMT

The setting Keep only latest feature for each Track ID value is functionally the same as Update a Feature in GeoEvent Server.

You don't need to make it a Velocity hosted feature layer with a pre-defined Track ID field for this to work.

If you already know which field/column is the primary key used to update existing records, you can use the Map Fields tool. In the tool, tag that field with TRACK_ID.

For example:

Re: Velocity - Update Attribute on Existing Record?

ArthurSmith2 — Tue, 03 Mar 2026 19:48:13 GMT

Thanks @Jeff_G and @JeffSilberberg!