In the Coronavirus Response solution, if I add custom fields to the Cases feature layer, do I have to recreate the three feature layer views from scratch? It does not seem you can update the views with new fields on the source feature layer.
Solved! Go to Solution.
FYI to everyone that you can't change the view definition for the cases standalone table from the visualization tab of the view. That tab only shows the layers with geometry and hides layers that are simple tables. So you have to add the view to a map, click the table in the contents and then click "set definition".
Mike, are you sure you don't mean a 1:Many attribute join? 1 report area to many case reports. When I do a 1:1 I don't see additional records.
Also, I've gone through all these steps and everything seems to be working except the dashboard. Survey collects data from the new field and I can see the data in the Web Map. But when I go to update the configuration of the dashboard the indicator elements just spin trying to find the layer never coming back with no-data or not configured message.
It's a 1:1 join because with Cases_current we're only returning the most recent case report from the Cases table, which is why after when doing a 1:1 join we see the Define which record is kept option and set that as Order by Date Reported, Newest.
Re: the dashboard. Unfortunately, the indicators you reference as spinning (and the dropdown) will need to be deleted and re-added, summing the appropriate field. This can be done relatively quickly. One tip would be to deploy a second Coronavirus Response Solution to reference indicator configurations. If deploying a second time, you might want to un-check the Use Existing Items in The Organization option in the Options hamburger menu.
Another option would be to use ArcGIS Online Assistant to find the item ID references to the Cases_current view shipped with the Solution in the JSON of the Community Impact Dashboard and replace those references with the item ID of your newly created Cases_current view. However, directly modifying the JSON of any item is risky and should only be done if you are confident and familiar with that sort of workflow.
Summarizing in one comment. Hopefully that's useful!
When adding a new field to the Cases feature layer the new field will need to be accounted for on the views created from the Cases feature layer. Getting the new field on the view depends on the type view:
To get that new field on Cases_current it will need to be recreated:
Cases_current or something similar.
Layer to join to the target layer:
Fields to match:
name = name
Join one to one
Define which record is kept:
Order by Date Reported / Sort by Newest