Latest Contributions by ChrisFox

@BryantDevillier, this issue was resolved last night in ArcGIS Online.  ... View more

Hi @TimBlanchard, with Citizen Problem Reporter we designed it to first show a list of existing reports/requests to help prevent duplicate requests from being submitted. Residents can see a pothole has already been submitted and click it to view its status and details rather than submitting a duplicate request. If you want to reduce confusion about the purpose of the list you could consider moving the Submit a Request button to the top of the pane by configuring the application, see the setting below on the Form tab. Another thing you could try is the text displayed for each existing report is defined by the pop-up title in the Citizen Problem Reporter web map. If you open web map in Map Viewer Classic you can modify the pop-up title. You might consider adding the timestamp with the request is submitted to better indicate it is an existing report. In terms of your second screenshot. This is the UI you get when you have multiple maps shared with the Citizen Problem Reporter group. The icon is the thumbnail of the map. In version 1.0 we switched from multiple maps and multiple layers to a single map and a single layer to simplify the user experience. I will say even in the previous version/UI when you clicked a problem category, for example Road Problems, you would still be taken into the same UI you are today. You would see the list of all submitted Road Problems and if you wanted to submit a new Road Problem you would need to click the Submit a Request button and fill out the form.  There is no way to skip the list of reports page when the user enters the app and just open the new request form. ... View more

@BryantDevillier, I was able to reproduce the issue. It seems to have started with the ArcGIS Online release last week. We didn't change anything to the application so we are looking into the cause of the issue now to see how we can resolve. I was able to narrow down that it seems to be specific to the Feature Layer editing setting I helped you with in a previous community post: https://community.esri.com/t5/arcgis-solutions-questions/modifying-citizen-problem-reporter-s-visible/m-p/1239288 When I change the setting 'What features can editors see' on the feature layer Requests_reporter to 'Editors can see all features' the app is able to load with no issues. I will reply back when we have an update on this issue. ... View more

@JamesBurton1, I see the issue. There is a bug in my script that we don't typically encounter because in the default schema we have the same field name for the addressptid in both the AddressPoint feature class and the SiteAddressPoint feature class. Looking at your script you have a different name: // Define the Address Points fields var id_field = "addressptid"; var offdist_field = "offdist"; var offdir_field = "offdir"; var numpoints_field = "numpoints"; var incrementval_field = "incrementval"; var capturemeth_field = "capturemeth"; // Define the Site Addresses fields var addressptid_field = "addressid"; The issue occurs later in the expression when we attempt to create a new SiteAddressPoint, I am referencing the id_field variable from the AddressPoint feature class rather than the addressptid variable for the SiteAddressPoint feature class: Push(adds, { 'attributes': Dictionary(id_field, id, status_field, defaultstatus, addrnum_field, addrnum, roadfullname_field, intersectingRoad[fullname_field], addrcapturemeth_field, $feature[capturemeth_field]), 'geometry': newPoint }) This is why it is saying the index addressptid doesn't exist, because that field doesn't exist in the SiteAddressPoint feature class. If you change that section of code to below, it should work: Push(adds, { 'attributes': Dictionary(addressptid_field, id, status_field, defaultstatus, addrnum_field, addrnum, roadfullname_field, intersectingRoad[fullname_field], addrcapturemeth_field, $feature[capturemeth_field]), 'geometry': newPoint }) ... View more