Example Flow - Update a Record in a Feature Layer

AaronPDXPaul

Does anyone have an example of a Flow that uses Update a Record in a Feature Layer?
No customization, just update a value from one field in a Sharepoint List.

The trick, I think, is in the Where Clause.
Getting a unique value in the List to match with a unique value in the Feature Layer.
We've tried many variations of text, numeric and so on, nothing works.

 

Thank you

 

VenkataKondepati

Hi @AaronPDXPaul ,

Here’s a clean “no-customization” setup you can copy.  There are two ways: 

A) Simple text key

Prep

• SharePoint List: add Single line of text column Unique_Field (use your Status if you want).

• Feature Layer: add Text field Unique_Field (same name), ensure layer editing (Update) is enabled.

Flow (Power Automate)

1. Trigger: When an item is created or modified (SharePoint).

2. Action: ArcGIS → Update a record in a feature layer

   • Where clause:

      

     Unique_Field = '@{triggerOutputs()?['body/Unique_Field']}'

     (Strings need single quotes.)

   • Attributes: set fields you want to update, e.g.

      

     Status = @{triggerOutputs()?['body/Status']}

3. Save → test by editing a SharePoint row whose Unique_Field matches a feature.

Notes

If your key is numeric, drop the quotes:

 

UniqueID = @{triggerOutputs()?['body/UniqueID']}

 

 

GlobalID key 

Prep

• SharePoint List: add GUID column FeatureGlobalID (or Single line of text if you’ll paste GUIDs).

• Feature Layer: use the built-in GlobalID field (ensure your layer has GlobalIDs enabled).

Flow

1. Trigger: When an item is created or modified.

2. Action: ArcGIS → Update a record in a feature layer

   • If your SharePoint GUID has no braces, add them:

      

     GlobalID = '@{concat('{', triggerOutputs()?['body/FeatureGlobalID'], '}')}'

   • If it already includes {}:

      

     GlobalID = '@{triggerOutputs()?['body/FeatureGlobalID']}'

   • Attributes: map fields to update (e.g., Status, LastEditor, etc.).

Tips

• Don’t use OBJECTID as the key (it’s not stable across operations).

• Test with one record first. In the Flow run history, check the ArcGIS action’s feature count updated.

• If multiple features match (they shouldn’t), the action may fail—keys must be unique.

• For bulk updates later, switch to Update records in a feature layer (batch) with the same WHERE logic.

That’s it. Start with A (text key) to prove the path, then switch to B (GlobalID) for production. If you paste your actual field names, I’ll hand you the exact WHERE line