Exploring Excel-Based Feature Layer Editing and User Types, Question

[JonJones1]

Hey everyone,

I’m new to Power Automate, and we’re transitioning from ArcGIS Online to ArcGIS Enterprise in a few weeks. As we make this switch, a common question has come up: Can we edit feature layer data through Excel?

I know ArcGIS for Excel is an option, but in ArcGIS Online, users needed a Creator license to pull in and edit an attribute table—which costs around $700 per year.

For ArcGIS Enterprise (we’re getting the Standard version), I’m looking into whether Power Automate can be used to:

• Connect to feature layer attributes
• Pull that data into Excel
• Allow updates to be pushed back to the feature layer

From what I understand, this should be possible—but does it still require a Creator license? Or does ESRI licensing not impact this, meaning even a Viewer could make changes?

I’m also curious about sharing this setup. If I configure the ArcGIS Enterprise connector to allow users to pull in and edit attribute tables, is there an easy way to share this setup with others? Not sure if I’m using the right terminology, but hopefully, my question makes sense!

Apologies if anything is unclear—I’m still learning. I’d really appreciate any insights!

[ShannonCardoza]

Its me again @JonJones1, I've reached out to my colleague regarding this question but he is on vacation. From what I gather, ArcGIS Connectors for Power Automate requires explicit Microsoft component licensing.

For many functions, your Microsoft 365 role should be set to Contributor or higher. We can circle back once my SME returns to office. 

All the best,

SC

[ArcGISforPowerAutomate]

Hi, If you have access to the ArcGIS Enterprise connector (you need an MS365 license with access to Premium; no special ArcGIS license is required), you can use it to export and import data to your feature layer from any source you can connect to, such as SharePoint, Excel, etc.

You can also use the Update record or Update records (batch) actions to push the new data into your Feature Layer. If you are working with a more data-intensive flow (say, more than 10 records), I definitely recommend using Batch.

Let me know if you have any questions. You can also use and Run data pipelines if they fit your architecture for more data-intensive flows.