Quelqu'un a-t-il un exemple de Flow qui utilise Mettre à jour un enregistrement dans une Feature Layer ? Pas de personnalisation, juste mettre à jour une valeur d'un champ dans une Sharepoint List. Le truc, je pense, est dans la clause Where. Obtenir une valeur unique dans la List pour correspondre à une valeur unique dans la Feature Layer. Nous avons essayé de nombreuses variations de texte, numérique, etc., rien ne fonctionne. Merci

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) * Trigger: When an item is created or modified (SharePoint). * 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']} * 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']} B) 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 * Trigger: When an item is created or modified. * 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

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Exemple de Flow - Mettre à jour un enregistrement dans une Feature Layer

AaronPDXPaul

Quelqu'un a-t-il un exemple de Flow qui utilise Mettre à jour un enregistrement dans une Feature Layer ?
Pas de personnalisation, juste mettre à jour une valeur d'un champ dans une Sharepoint List.<\/P>

Le truc, je pense, est dans la clause Where.
Obtenir une valeur unique dans la List pour correspondre à une valeur unique dans la Feature Layer.
Nous avons essayé de nombreuses variations de texte, numérique, etc., rien ne fonctionne.<\/P>

<\/span><\/P> <\/P><\/span><\/P>Merci<\/P> <\/P>

Trouver plus de publications taguées avec

Accepted answers

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)

Trigger: When an item is created or modified (SharePoint).
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']}
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

Trigger: When an item is created or modified.
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

All comments

AaronPDXPaul

This is fantastic.
Esri support and myself independently followed your steps with success.

Something has changed in connecting the Unique ID's from 2022-23ish.

I have the same issue with all my connectors that used to work,
The logic is correct, no errors, but the List and REST aren't in sync.

I'll create a post for each Flow.

Thank you again,
Aaron

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)

Trigger: When an item is created or modified (SharePoint).
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']}
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

Trigger: When an item is created or modified.
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

Akshay Harshe

@AaronPDXPaul Looking at your screenshot, are you updating an existing older flow? We updated the `Get data from feature layer action last release and it should include more options with different option names and placeholders, which I don't see. Try deleting and recreating the action. In Get data from feature layer action you can choose to use a `Where` clause but I think syntax should be something like

ObjectID=1234

Or if you are using dynamic content then:

Here is a simple example. I agree with all the comments made by @VenkataKondepati this is basically what he mentioned in a flow just using OBJECTID which in my case is FID

Hope that helps.

AaronPDXPaul

This is awesome.

Rather than dissecting what I did.

Can you give direction on what to set up?
I'm just trying to get the logic to work, no customization.

Like a text field in the list called "Unique_Field"
Mine is really called "Status".

That would match with a Text field in the Feature Layer called "Unique_Field"
Or it can match with GlobalID if that is what works best.
In that case, I'd change the field type in the List to a GUID.

So, I don't have any specific fields needed or criteria to follow.
Just want to see it work for now, then I can redesign.

Thank you

VenkataKondepati

Use the ArcGIS Power Automate “Update a record in a feature layer” action and drive it with a WHERE clause that follows ArcGIS REST SQL. Pick one stable key shared between SharePoint and the feature layer (ideally GlobalID). Don’t use OBJECTID.

Flow outline

Trigger: SharePoint “When an item is created/modified”.
Action: ArcGIS → Update a record in a feature layer
- Where clause examples:
- String key: parcel_id = '@{triggerOutputs()?['body/ParcelID']}'
- Numeric key: site_id = @{triggerOutputs()?['body/SiteID']} (no quotes)
- GlobalID (GUID text in SharePoint): GlobalID = '{@{triggerOutputs()?['body/FeatureGlobalID']}}'
- Date (if needed): edit_date >= DATE '2025-08-01'
In the action’s Attributes section, set the field(s) to update from SharePoint dynamic content.

Tips

Ensure the key field is unique in the feature layer (GlobalID is safest).
If your GUID in SharePoint lacks braces, add them in the expression: concat('{', <guid>, '}' ).
For strings with quotes, wrap in single quotes; for numbers, no quotes.
If you’re updating many rows, use “Update records in a feature layer (batch)” and specify the unique ID field.

If you share your key field names (SharePoint vs feature layer), I’ll hand you the exact WHERE clause and attribute mapping.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.