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; } } }

'Update record in feature layer' action - no longer takes domain code for field update?!

NataliyaLys

I have a number of flows set up that connect to data in AGO, listen for the feature updates, then send emails, and update email_status of the features after an email has been sent.

Yesterday (6/13) I needed to make a minor change to one of the flows (remove one value from the Condition), and when I tried to save the flow I got an error indicating that I have wrong value in the 'Update a record in a feature' action, the error basically indicated that I should use the domain description instead of domain code value.

I made the changes throughout my flow, and was able to save it sucessfully. But my flow now doesn't recognize the updates to the email_status, and it keeps getting fired when updates are made.

Was there a recent update to the Power Automate ArcGIS actions that would cause this?

Also, I would really appreciated any suggestions on how to fix the issue. Thank you!

Find more posts tagged with

Accepted answers

All comments

NataliyaLys

@Pavel148 Thank you for fixing this.

Pavel148

@RobertAnderson3We plan to redo how domains are handled in a later release to prevent breaking existing flows.

RobertAnderson3

Amazing @Pavel148 thank you for such a quick turnaround on this!

I see in the parameter it shows the descriptions, not the domain codes. If we put in the description or leave the options from the dropdown lists, will it apply the domain value or the pure text like it has been?

That said, I do like the idea of the dropdown being there, it just needs to pass the information correctly to store the domain code.

Have a great weekend!

Pavel148

@NataliyaLys @RobertAnderson3
We pushed a fix for the coded values in Create a record in a feature layer and Update a record in a feature layer. Previously existing flows should be working, and the dropdown will not be available.
Available values will be shown in the parameter description, but other values will be supported.

Please feel free to reach out here or at powerautomate@esri.com if you have any questions or suggest improvements to better support your flows.

RobertAnderson3

Hi @Pavel148 thank you so much for letting us know that you're working on fixing this! Is there a BUG that we can have support attach us to? I had opened a case with Esri Canada the other day.

Please keep us updated!

Pavel148

Hello, thanks for reporting this! We are working on a fix, and it should be done soon.
Let us know if you need any support while we work on it.

RobertAnderson3

I have just encountered this exact same issue and it is causing me a lot of grief right now, it wouldn't let me save with the domain codes typed in, so I changed the selections to the drop down list the action provided (appreciate that new functionality) as well, but now it's not storing the domain values, it stores the description, which messes up the data and breaks symbology in the maps it's being used in.

I am not using the Update action though, I am using the Create action. And this is true for both the new and classic automate designers.

@SeanKMcGinnis any insights to if there was an update or if there's any resolution for this?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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