Cannot submit report on Crowdsource Reporter

[EmilyLee]

Hello,

Does anyone have any idea of what the problem might be if I receive the following message on Crowdsource Reporter please?

Thank you,

Emily

[AllisonMuise1 · Accepted solution]

emlee‌

This message usually occurs because the values you are trying to write to the service are invalid in some way that the normal form validation can't catch earlier - usually because the problem field hasn't been included in the form. The most common reason for this is a field that is required, doesn't have a default value, and is not included in the Reporter form.

If you think that you have all required fields without default values exposed in the form, you can double-check this by enabling editing on all fields in the popup configuration. Required fields will be easily visible in the form, along with their default values (if any). Try submitting a report with all fields on. If that works, one-by-one turn off each field you don't want exposed in Reporter - saving the map, refreshing Reporter, and submitting a report each time.When you get the error message again you'll know which field is causing the issue.

To resolve it, you'll need to either include that field on the Reporter form, make it accept null values, or provide it with a default value in the editing template prior to publishing.

If submitting a report with all fields turned on fails as well, let me know.

[EmilyLee]

Thank you very much for your reply Allison.  I re-did everything with the following steps and it worked. 

1. Add the feature service to a new webmap with full editing control.

2. Save the webmap > Share with public and the Group.

3. Go to the Group > SHARE > CREATE A WEB APP > Select Crowdsource Reporter.

Thanks again!

Emily

[RyanHughes3]

Hi Allison,

I am running into the same issue. When I submit a test report, I receive the same error message. However, if I reload the app, the report I submitted will be visible on the map and on the sidebar. I believe every field that needs to be editable and displayed is set properly. The only fields not shown are default (FID, GlobalID). See the screenshot. The displayed fields are "Comment", "FirstName", and "LastName".  

For debugging, I deleted the app and created a new one following the same steps that Emily Lee reported, and the "Report could not be submitted" error still showed up. I have gone through the settings of the feature layer and the app, as well as the settings of the feature layer in the webmap, and I cannot figure out which (if any) settings need to be adjusted to fix the issue. Any ideas what is going on?

Thanks - Ryan

[AllisonMuise1]

Ryan Hughes‌ : Can you share your app, map, and layer with Everyone and either post or message me the URL to your app?

I'd like to take a look at the browser traffic when you submit a report. I'm puzzled by the fact that your report shows up even though you get the error message. Haven't seen that before.

[RyanHughes3]

Yep! Here's the app: https://clarkdietz.maps.arcgis.com/apps/CrowdsourceReporter/index.html?appid=b4ba92be86ae4694bb16e8a...

The map and layer are both shared with everyone as well. I also noticed that a static reference layer I have in the map only shows up in the inset map in the report form, not in the larger map. Let me know what you think!

[AllisonMuise1]

ryan.hughes‌ I think there are a few things going on here:

1) I think the schools not showing up in the main map has something to do with how that particular layer was created. When I look at the item details for that layer it says that the source is a feature collection instead of a feature layer. Now, that SHOULD work in both maps, but try publishing the layer as a feature layer and see if that makes a difference. I've made a note to investigate this further on my side as well.

2) I played around with submitting reports to your layer under various circumstances

- your app, your map, your layer = fail message but feature showed up on refresh

- my app, your map, your layer = fail message but feature showed up on refresh

- my app, a copy (Save As) of your map, your layer = success!

From this, it seems that something strange is going on with your map. Try doing a 'Save As' on the map and sharing that copy with the group. Can you submit a feature to the new map?

3) I'm not sure what this item is, but I cannot access it as an anonymous user. This may or may not be related to other issues you are seeing but I thought I'd point it out: https://clarkdietz.maps.arcgis.com/sharing/rest/content/items/af6448495d714d87a74151a0ac1a4a6d/data?... 

[RyanHughes3]

AMuise-esristaff‌ Ok - that worked after two attempts:

1) Save As on the map, shared it with the group, and removed the old basemap from the group = fail message but feature shows up

2) Completely new map, added the "public_input_points" feature layer, shared it with the group, and removed the copied basemap above = success!

Next, to test the 'schools' layer, I added that to the new map, refreshed the app, and received a submission failure again! So, as you started to figure out, there must be something wrong with the schools feature collection.

Next, I uploaded the 'schools' data as a shapefile (from a local zip) directly to the new map. When I refreshed the app, the schools only show up in the inset map, and the report form submission fails again.

Finally, I published the 'schools' shapefile as a feature service, added that to the map (and removed the shapefile), refreshed the app, and everything works! The schools show up in both maps, and the report submits correctly! The 'schools' feature service was from a feature layer this time, not a feature collection.

That was a lot of strange debugging, but I really appreciate your help! Hopefully this is a helpful test case and you can determine why the schools only appeared on one map, and why that data would be preventing my app from accepting new data points for the only editable layer.

Thanks again! And let me know if you need any more feedback.

[AllisonMuise1]

That is very weird, but I'm glad it's working! I appreciate the details on what it took to get there. I will look into this more and try to get a fix into an upcoming release.

-Allison

[AllisonMuise1]

I've verified that a fix for this will be included in the next release. With the next AGOL release, feature collections will be supported as reference layers in Crowdsource Reporter.