Looking for help with a Send Error in Survey123. You can see the error below, and I've attached the xls form too.
Hi Rachel,
I just had a look at your xslx file and now I see the problem. It appears you are using several geopoint questions all in the same layer, this is not supported. As per ArcGIS feature layers, there can only be one geometry field. Each geopoint question (or geotrace or geoshape) is a geometry field, so you can not have more than one in the same layer.
If you want to use more than one map question (geopoint) to collect data, you need to put them in seperate layers, via a repeat, or you can use the "null" esri field type, so that the question can be used in the survey, but the data/geometry not stored in the feature layer.
Regards,
Phil.
The screenshot of the error doesn't appear to load and/or is just showing a grey circle.
Are you seeing this error in the web app pr field app? Can you confirm the version you are using, and what version on the website is set in the settings? Do you have version locking on? What was last version the survey was published with?
Also did you create this survey with web designed or Connect?
Hi Phil,
Thanks for taking a look.
The error is coming up in the field app (version 3.9.149). In the website settings, version locking is on and was published under version 3.9. The survey was created using Connect.
Attempting to share the error again. Hopefully it comes through this time.
Thanks again,
Rachel
Are you using AGO or Enterprise, if Enterprise what version of Portal and how is it configured?
How did you create and publish the feature service, was it existing or new? If existing how was it created? It seems something is wrong with the geometry for the feature layer?
Have you ever been able to submit a survey to this feature layer from the field app?
I am using AGO. This is the first survey I've ever created and it's a new feature service, and I've never been able to submit a field survey.
-Rachel
I was beginning to think that was the issue when you mentioned something was wrong with the geometry, and that make perfect sense. I'll follow your recommendation for the null esri field type.
Thank you for all your time and help.
I'm having a similar issue with my own survey, however, the bind::esri:fieldType is set to null for all but 1 of the 4 total geometry types in my survey (3 outside of a repeat, 1 inside a repeat). The geometry question that I have without null as the fieldtype is a polygon type (geoshape) outside of the repeat. Could you share what you think may be going on here? I am still getting the same error as described above.
Leigh
Hi @Anonymous User,
Similar to 'leightmaes' question below. I have a survey with multiple geopoint questions but all but one having "null" in the bind::esri:fieldType column but when I try to submit a survey I receive the following error "No mapping exists from object type ESRI.ArcGIS.Client.Geometry.MapPoint to a known managed provider native type."
Any idea why this might be occuring?
Cheers
Hi @JamesBailey,
When you published the survey, was the first geopoint question null field type? In that case did it create a table only, not a layer, meaning there is no geometry?
You can check the schema in Connect and the Schema tab, so see if it is a table or layer. It sounds as though you have a table, but are trying to send geometry via the geopoint to the table.
Hi Philip,
I created the survey with two geopoints and one geotrace. The geopoints are not stored (null field type), they are used as start- and endpoint of the geotrace. In connect I see that a table is created, not a layer.
If I move the geotrace question above the point questions, a layer is created. But, I need it to come after the geopoints.
So, how can I do that? How can I "force" survey Connect to create a layer even if my first geopoint question is a null field type?
Tom
Hi @TomDe_Leus1,
Depending on the type of layer you want (geopoint, geotrace, geoshape) put that question first in the survey for that parent or repeat, so that Connect creates the layer with that geometry. After the first successful publish and creation of layer with correct geometry, you can move the null geopoint questions above the geoshape in the XLSForm. When you publish the survey the second time with new order, it will not change the geometry but the other of the questions in the survey form will reflect the new order.
@Anonymous User - Your recommendations worked for creating the feature layer initially via Connect, but Survey123 is submitting geoshapes with null geometry if the geoshape question is moved to a row lower than a null geopoint after initial publishing.
My first geo question is a geopoint set to null, then I have a repeat with a geopoint in it, then a geoshape that's calculated from the min/max lat/lon values extracted from the repeat. If I publish the survey with the first geo question being null, I end up with a table and an error message that matches the original poster of this thread. Your recommendation to move the non-null geo question to the top for initial publishing fixes this issue.
If I do a test submission without changing this order of questions, the geometry for my geoshape is stored.
If I move it lower than the null geopoint (and the repeat that contains another geopoint), submission succeeds but the geoshape geometry is null.
If I move it back up to the top of the form, the geometry is included in the submission.
If I move the first null geopoint below the geoshape (and the repeat table), the geometry is once again included in the submission.
I've tried this a few times now, including publishing a new survey multiple times. I also queried the feature layer to make sure it wasn't just an issue with the map viewing visualization. I'm using Connect 3.13.234, fyi.
Pictures:
1. Query on first submission, OID1, before moving the non-null geoshape question at the top of the form. 2 & 3. Query on OID2 & 3 after moving the geoshape below the null geopoint. OID2 is automatically created with my calculation. OID3 was a manually created polygon in the app. (extent_acres is one of my calcs on the geoshape, so you can tell the app is recognizing it)
4. Query on OID4, after moving the null geopoint to the bottom of the form (and under the repeat), making the non-null geoshape the first geo question in the form again. Geometry is included on submission.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
