Allow 'Create Feature Layer' action in Power Automate to publish a table. Currently, the action asks for a location field, defaulting to 'Automatic: Find in File'. An option to treat the input as a table and not a spatial feature layer would be helpful for non-spatial table data or for table data with inconsistent location info.
Use case: Publishing a table from a SQL Server, lat/lon fields are user input and can contain errors. Ideally, I could publish the table, then use an AGOL Notebook to generate shape and create or update a Feature Layer.
Alternate case: Table contains tabular data with an ID field that can be joined or referenced by other AGOL datasets. No location required or needed.
Awesome idea Scott.
I think this is a really great idea. We are starting to plan for upcoming workstreams and will add this to the list of capabilities for us to consider.
Thanks again and keep them coming!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.