Geocoded SharePoint data displayed dynamically in ArcGIS online map
This is going to be a bit lengthy, so bare with me. I will include a picture of an overall example flow
This example operates for individual additions to a SharePoint list. If you bulk add items, it may be more effective to use a timed/manual trigger and then use the "Get Items" action with an appropriate query to pull the data. If you use this method, the following steps would just need to nested inside of a "Apply to each" action so that it loops through each row that was added to the list.
The first step will be to parse your X and Y variables from the location attribute in the list. In the example, my coordinates are listed as ['DispName'] in the body as a pair in string format. So, I parse those and convert them to a float as follows:
After I have my x and y coordinates parsed and available, I find it a best practice to initialize a new variable to create the JSON for my feature. Just remember that when you add string data into the attributes section from your list item response, you need to surround it in quotes for proper JSON syntax:
Once you have the feature json definition ready, you can generate a token, and sent the POST request to add the feature to your AGOL layer. (If you are doing a batch of features instead of one, you should move the generate token action to before your "Apply to each" action set so that you aren't creating unneeded overhead). So first, generate your token:
Then, you can send the POST request to add the feature to your hosted feature layer using the token from the previous request and the json object created for the new feature.
Finally, it is a good idea to keep a column on your sharepoint list for the hosted objectid. Once you add the feature, the JSON response will include the objectid for the created feature that you can use to update your list item. This will be useful later if you want to set up other flows to update or remove items on the hosted feature layer using the editFeatures method.
One final note to keep in mind is that the standard geometry pair that is given with sharepoint geometry is WKID 4326. If your hosted feature layer is not in this spatial reference you will need to add a request into the flow to use the project utility from Arcgis or some other service that would allow you to project the coordinate to the required reference.
