Citizen Problem Reporter Solution

[cmerwin]

Hi all,

I’ve recently redeployed the Citizen Problem Reporter solution for the third time now, and I’ve noticed that with each update, the Esri Solutions team continues to improve and streamline the experience. I really appreciate the ongoing work. It’s been great to see the evolution, especially the new integration with Field Maps Designer forms.

However, with this most recent deployment, it looks like the address field is no longer included by default. Everything appears to be handled through the Field Maps form configuration now, which is a solid improvement overall. That said, I still need an address field that is automatically populated through geocoding.

In previous deployments, I may or may not have had an Arcade expression that pulled the address into a field. Honestly, I don’t remember for sure. But regardless, with the new form setup, I simply do not know the current workaround for getting that address information into the dataset when the features are created through a field maps form.

This is important because I have a workflow set up in Microsoft Power Automate that sends notification emails when a new report is submitted. Those notifications rely on having a clear geocoded address included in the form data.

Has anyone else deployed the latest version of the solution and figured out how to get geocoded addresses (for example, from a dropped point) into a field that can be accessed in automation workflows? I’ve noticed some editing capabilities are limited since this is a managed solution, so I’m hoping someone has found a workaround that works with the latest changes.

Thanks in advance for any advice or insights.

Kindly,

cmerwin

[ChrisFox]

Hi @cmerwin, unfortunately the ability to reverse geocode a point to get the address from the feature is not available in Arcade at this time. This is why this feature is not available yet as you have described we have focused on doing as much as possible within the form configuration in the layer rather than having custom functionality in the app itself. We are hoping this feature is added to Arcade in a future release and then we will be able to support it in the solution out of the box.

One option since you are already Microsoft Power Automate is to use the Reverse geocode action that is available directly in Power Automate. In your flow you could do this before sending the e-mail to get an address from the point. You could also use the flow to update the location field on the feature.

https://doc.arcgis.com/en/power-automate/latest/automate/actions.htm#ESRI_SECTION1_C30D73392D964D51A...

[MatthewMalone]

Hi Chris,

I recently deployed the new CPR solution on our org and was very confused why the location field was blank in the Manager.  Since the location info is essential for anyone reviewing the submissions, I'm now going to hold off on rolling it out.  Mainly since I know I'll receive a lot of emails from staff asking, "So, what is the address?"

With that in mind, I'm open to learning the reverse geocode routine.  Any chance Esri could put together a step-by-step on the Power Automate steps needed for the reverse geocode?  Based on earlier conversations we had, I secured a PA premium license to try the email generation script, so I could hopefully muddle through a reverse geocode process as well. 🙂

Thanks!

-Matt

[ChrisFox]

Hi Matt,

This is a good suggestion to provide additional documentation for this scenario. We will look at this for a future update. Until then, I think you can leverage the existing documentation for sending emails with Power Automate to start your flow and then just tweak the flow to do a reverse geocode as well.

Below is a screenshot of my flow to get this working and I have highlighted the settings I use for the reverse geocode step.

Then after the reverse geocode I am using the Update a record in a feature layer action to update the original feature's location field with the result from the reverse geocode.

Hope this helps you get this implemented in your organization.

-Chris

[MatthewMalone]

Hi Chris,

Thanks for the prompt response and the screenshots to help me with the reverse geocode.  I'll be plugging through Power Automate to see if I can get both routines up and running.  I appreciate the help!

Thanks again,

-Matt

[MatthewMalone]

Chris,

I'm happy to report that the reverse geocode process worked successfully! As we discussed regarding the email generation, the current procedure requires using the new Power Automate designer versus the default one.   Once I had that up and running, I was able to insert the reverse geocoding portion using the parameters you included.  Hopefully your posts will help the original poster of this thread to make it functional with their CPR data.

Thanks again,

-Matt

P.S. I also added a section in the PA flow to change the visibility to public to "No," which we had in the prior CPR to prevent anything inappropriate from being posted.  I'd be happy to share that if it's helpful.

[ChrisFox]

Hi Matt,

That is great to hear. Another option for setting Public View to 'No' by default is to update the calculated expression for the Visible to Public field in the edit form configured in the Citizen Problem Reporter web map. This expression just returns 'Yes' by default, but you can update it to return 'No'.

Another thing if you want to go a step further is I experimented with using the OpenAI connector in PowerAutomate to use ChatGPT to review the details text in the request and determine if it contains any inappropriate language or content. If so, it returns 'No' that I then use to update the Visible to Public field, otherwise it returns 'Yes'. I was having pretty good success with that. Thought it was an interesting pattern that had other potential uses as well in this workflow.

[MatthewMalone]

Hi Chris: That's an interesting thought on the ChatGPT angle, but I'm honestly just glad it's working at this point. 🙂  I wasn't aware of the edit form on the web map as I've yet to explore all the details of the solutions' functionality.  Thanks for pointing that out as an option.

-Matt