Latest Contributions by MikeDagle

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: Cases_public   is just a basic view of Cases with editing turned off in Settings (used in the Community Impact Dashboard) Cases_reporter   - as above but with editing turned on (used by the Case Reporter survey) Cases_current   - a join view returning the most recent report for a reporting area.  A new field can be exposed on the existing Cases_public and Cases_reporter views, whereas Cases_current needs to be recreated. Let's look at exposing first: In all likelihood a new field will be added to the Cases table which means the method of defining the fields exposed to the view using Visualization tab on the item page will not work. However, we can add the table to a map to set the view definition: Add a new field to the Cases table in the Cases feature layer. Navigate to the Cases_public or Cases_reporter view in your contents. Click the Open in Map View down arrow, then Add to new map. Click the More Options ellipses on the Cases, then click Set View Definition. Click Define Fields. Scroll to the newly created field, check the box. Click Apply. The new field is added to the view’s definition. To get that new field on Cases_current it will need to be recreated: Add the Cases feature layer to a new web map. Click Analysis, Summarize Data, Join Features. Configure the join in this way (Note on naming the new view: to name the new view Cases_current, the existing join view would need to be deleted. However because of subsequent steps, it would be advantageous to leave the current Cases_current view in place and use a new name): Name: Cases_current or something similar.  Target: Reporting Areas Layer to join to the target layer: Cases Fields to match: name = name Join Operation: Join one to one Define which record is kept: Order by Date Reported / Sort by Newest Update the Community Impact Dashboard indicators and selector dropdown to use the new join view. This will require reconfiguring some of the dashboard elements. Because of this, a good workflow is leaving the existing Cases_current view in place, save a copy of the dashboard for configuration reference, update the original dashboard to use the new view.  Mike ... View more

Hi Jennifer Borlick, Apologies for the delay on this thread. I'd recommend re-deploying the solution (make sure you uncheck the Use Existing Items In The Organization in the Options menu of the Deploy an ArcGIS Solution step). Then test to see if you still receive the insert duplicate error.  I'll keep an eye on this thread so feel free to ask follow up questions.  Mike ... View more