Latest Contributions by ChrisFox

The categories and types are in the CSV. The notebook reads from the CSV and updates the feature layer. If you run the notebook as is, when it completes the layer will updated and you can see this in the Reporter app. I would really encourage you to run through the help steps, there are only a few and will get you up and running quickly. ... View more

No it does not come preconfigured with request categories and types. In addition, it is not just controlled by domains. We are actually using contingent values in the feature layer. Contingent values are what give you the behavior where if you select a specific request category it limits what the valid values are for the request types. It is not currently possible to populate contingent values through the UI, however we provide a python notebook that can be run to update the contingent values on the layer. In addition, we provide a CSV file that can be downloaded and modified to include the desired combinations of categories and types. The notebook reads from this CSV to update the layer. The CSV is preconfigured with a base set of categories and types. I would recommend you follow the documentation to download the CSV and review the categories and types. Make any desired changes, save and upload it back to the item. Then you can run the notebook to apply the contingent values to the layer. ... View more

We document how to import and modify the request categories and types in the documentation link below for version 3.0 of the solution: https://doc.arcgis.com/en/arcgis-solutions/latest/reference/configure-citizen-problem-reporter.htm#ESRI_SECTION1_64BA96A144634860A104787C94FFD308 ... View more

I took a look and this is occurring because the Requests layer has no templates. You should be able to go into the map viewer and edit the templates on the layer. Make sure you add one template, this will be the default template used when submitting new requests. If you have more than one template you will be presented the option to select the template as you saw before. ... View more

Yes, it looks like it is stuck on the template selection page, but there are no templates displayed. Is this shared publicly? Anyway I could get access to app/map/layer to see what is configured. If you would prefer to shared privately you can send me a direct message. ... View more

Hi @Dawn_Scott, With regard to the form only showing the legend, my guess is that the feature layer now has multiple editing templates and it is asking you to select which template you want to use first. If the layer only has one template it skips this step and takes you right to specifying the location and then filling out the form. Could you share a screenshot of what you are seeing. With regard to the location field, unfortunately there is no way through Arcade to reverse geocode a location to get an address. It is also not possible to do this in the new version of the Reporter app. We are looking into options for this in a future release, but I would also point you to another community post where I discussed using PowerAutomate to reverse geocode the report location and write it to the location field for each new report. https://community.esri.com/t5/arcgis-solutions-questions/citizen-problem-reporter-solution/m-p/1639395   ... View more

Thank you for submitting this idea. We are working on adding support for this in a future release of Enterprise. I will update this idea when we have more clarity on when this will be available. ... View more

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.   ... View more

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 ... View more

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_C30D73392D964D51A8B606128A8A6E8F ... View more

@JohnWatermolen_OCGIS, the error you are seeing was introduced at Pro 3.4. If you deploy the latest version of the solution (v2.4) in AGOL you can get the latest version of the tool that resolves this issue: https://doc.arcgis.com/en/arcgis-solutions/latest/reference/introduction-to-address-data-management.htm#ESRI_SECTION1_8D48881D377E452FA8E22A939FBBF1F6  ... View more

@Alex_755, we recently added the ability to visualize the solution items and their dependencies via a diagram in the Solutions app. From the My Solutions page you can click the 'View Diagram' button. The diagram will display the items and draw arrows between dependent items. You can select an item in the diagram to highlight its dependencies. This functionality is available in ArcGIS Online and Enterprise starting at 11.5. ... View more

@dsinha, I think I understand now. You would like to know if you can deploy the solutions now at 11.2 and minimize the amount of work you need to do at 11.4 to get the updated versions. I will say it will depend on the solution. The best way is to refer to the documentation and compare the version and release notes between 11.2 and 11.4. For example, the Plans and Drawings and Lead Service Line Inventory solution have not changed between 11.2 and 11.4. So you can deploy it now and won't need to do anything at 11.4. For other solutions like Public Parking, or Stormwater Data Management there was just a minor version change between 11.2 and 11.4 (ex. 1.0 -> 1.1). In this case we just updated the apps and made no changes to the feature layers. So if you deploy it now and load your data into the layers, you can deploy the update at 11.4 and it will just create new apps on top of the existing layers. There will be no need to move data to new layers. For other solutions like Special Event Operations there was a major version change between 11.2 and 11.4 (ex. 2.2 -> 3.0). In this case the 11.4 version will deploy new feature layers in addition maps and apps. You can't just swap out the new layers for the old layers because we introduced schema changes that are required for the solution to function as expected. So my recommendation would be to start with the solutions that don't change between the versions first. Then you can move to the solutions that have just a minor version change, because the work you do now to load and create your data will continue to work when you deploy the update at 11.4. Finally you can deploy the solutions that had a major version change now, but understand that migration will be a little more involved once you deploy the update at 11.4. It will evolve loading data from the old layers into the new layers and potentially populating additional attributes as needed for the solution.     ... View more

@dsinha, could you provide a little more information on the issue you are running into, what solution(s) you are using, and what you are hoping to accomplish?  ... View more