topic Re: Fields not found in the feature service: 0 in ArcGIS Survey123 Questions

Fields not found in the feature service: 0

EddyClark — Wed, 09 Nov 2022 17:44:08 GMT

Fields not found in feature service

Log File:

filename="PublishServiceCheck.qml" line="73"] qml: Check result: {
"compatible": false,
"reason": "Fields not found in the feature service: 0",
"newFields": null,
"updateFields": {
"updateFields": [
{
"layerUrl": "https://...

Re: Fields not found in the feature service: 0

ErikHerbergMETC — Wed, 09 Nov 2022 20:58:29 GMT

Same issue here. This just started happening. I can't update and republish any of my forms now.

I'm guessing it's related to the recent update because I was republishing using a submission_url just fine as recently as last week.

Update November 7, 2022
This update includes changes to Survey123 Connect, the Survey123 field app and web app, and the Survey123 website.
Survey123 Connect (version 3.16.106)
Fixed a bug in which some publishing errors were not displayed when using a submission URL.

Re: Fields not found in the feature service: 0

sth_eagle — Wed, 09 Nov 2022 21:02:42 GMT

Likewise, we have struck the same issue. The survey was working fine yesterday, then the user came back from lunch and started having this problem.

Re: Fields not found in the feature service: 0

MadisonCounty1 — Thu, 10 Nov 2022 13:43:11 GMT

Same here. The issue started after our MS store app updated to 3.16.106.

Re: Fields not found in the feature service: 0

JenniferAcunto — Thu, 10 Nov 2022 13:50:35 GMT

My teammates ran into this the other day. They figured out it was because there was a mismatch between the field aliases for the feature service and the Survey123 label values. Their workaround was to put the aliases as they appear in the feature service in the bind::esri:fieldAlias column.

FYI @Ismael

Re: Fields not found in the feature service: 0

MadisonCounty1 — Thu, 10 Nov 2022 14:05:07 GMT

Thanks, workaround did the trick.

Re: Fields not found in the feature service: 0

ErikHerbergMETC — Thu, 10 Nov 2022 17:01:59 GMT

Worked for me as well, thanks! I've never used the bind::esri:fieldAlias column before, so I just plugged in the aliases into that column and then I was able to republish again.

I did a bit of experimenting and found that it wasn't needed for all "type"s, but I didn't do enough testing to figure out the exact pattern. For example, I noticed I had to fill in the bind::esri:fieldAlias column for text and select_one type questions, but I didn't for other types, including calculate, start, end, deviceid, and hidden. But I just filled in bind::esri:fieldAlias for everything included in my feature layer just to be safe.

Re: Fields not found in the feature service: 0

BarbaraWebster1 — Thu, 10 Nov 2022 18:11:37 GMT

Hi @EddyClark,

We can confirm that this issue was introduced in Connect 3.16.106 and occurs when the question label does not match the field alias in the feature layer.

The Survey123 team is working on a fix for this now, and we will update this thread with any updates regarding the fix. In the meantime the best workaround is the one already identified in this thread, which is to enter the field alias into the bind::esri:fieldAlias column.

Thank you,
- Barbara

Re: Fields not found in the feature service: 0

JasonJordan00 — Sat, 12 Nov 2022 15:54:27 GMT

This is occurring to me as well for any fields that are hidden. I've confirmed bind:type and esri:bind:type are correct as well as the alias. Toggling between hidden or text is the difference whether or not it will publish.

Re: Fields not found in the feature service: 0

BarbaraWebster1 — Mon, 14 Nov 2022 19:10:08 GMT

Hi @JasonJordan00,

Thanks for raising this question. I was able to reproduce the behavior you're seeing where a hidden question results in the 'Fields not found in the feature service: 0,' however when I enter the field alias into the bind::esri:fieldAlias column, the error does not appear during publishing.

By default hidden question types set both the field name and field alias to the question name, so if the field alias in the feature layer does not match the question name in the XLSForm, that is triggering the error message.

Can you try entering the field alias as it appears in the feature service into the bind::esri:fieldAlias column?

We will be sure that this use case is included in the fix for Connect.

Thanks,
- Barbara

Re: Fields not found in the feature service: 0

ErikHerbergMETC — Mon, 14 Nov 2022 21:13:10 GMT

@JasonJordan00 - Thought I might detail my experience in case it helps you in any way.

When I was troubleshooting my forms, I also thought hidden type questions were part of the issue, but then found out that wasn't actually the case. I had all of the aliases filled in and still wasn't able to republish. So I went through and deleted chunks of rows in my XLSForm at a time, trying to republish after each removed chunk. Eventually I could republish, which helped me narrow down to the exact rows/fields causing the issue.

Turns out that in one row (a hidden field), I had a typo in the field alias in my feature layer. Once I fixed that so it matched what I had in the bind::esri:fieldAlias column, like what @BarbaraWebster1 mentioned above, I was able to republish.

In another situation (again a hidden field), I could not see any different between what I had in the bind::esri:fieldAlias column vs. the alias in the feature layer - they looked identical. But I knew something about that row was blocking the republishing. So I tried editing the feature layer alias by copy/pasting directly from what I had in the bind::esri:fieldAlias column, and then it worked. Not exactly sure why it worked - maybe I had a phantom space or something.

Re: Fields not found in the feature service: 0

ctgb_Caleb_Smith — Tue, 15 Nov 2022 06:05:15 GMT

I am having the same issue as well, however, entering the field alias into the "bind::esri:fieldAlias" column does not resolve the error for me. I confirmed this by generating a new survey from an existing feature service, copying all of the values from the "Label" column to the "bind::esri:fieldAlias" column. Any ideas on how to work around this?

Re: Fields not found in the feature service: 0

BarbaraWebster1 — Wed, 16 Nov 2022 17:57:07 GMT

Hi @ctgb_Caleb_Smith,

Can you provide a diagnostic log file for this? If you start logging, trigger the error message by attempting to republish the survey, and then end logging, the diagnostic log file should give us some more information on what might be causing the conflict.

Thanks,
-Barbara

Re: Fields not found in the feature service: 0

ctgb_Caleb_Smith — Wed, 16 Nov 2022 20:28:29 GMT

Hi @BarbaraWebster1 , thank you for looking into this! I attached my log file, any help is much appreciated.

Thanks,

Caleb Smith

Re: Fields not found in the feature service: 0

BarbaraWebster1 — Thu, 17 Nov 2022 17:37:36 GMT

Hi @ctgb_Caleb_Smith,

Thanks for sending the log. It looks like the alias for the 'Retain' field in the feature service is being passed to Connect as null so this is being read as a mismatch and triggering the error. This may be what @ErikHerbergMETC was running into too. Can you see if editing the field alias in the feature service and overwriting it with the same alias value resolves the behavior you're seeing?

Thanks,
-Barbara

Re: Fields not found in the feature service: 0

Nabaz — Mon, 21 Nov 2022 11:50:37 GMT

All,

just wanted to elaborate on one thing. After copying and pasting "Field Aliases" into "bind::esri:fieldAlias" I was able to republish all of my forms except one them. finally I figured out that I had a trailing space in one of the field aliases and a double space between words in another one .
Although those spaces where existing in both places i.e xlsForm and Feature service, but I was still getting the error and wasn't able to publish. After removing those spaces in both places I was able to publish the form again.

you can use below method to identify the extra spaces in the xlsForm.
1- click on a blank cell (eg. A1) and go to conditional formatting.
2- Create a new rule --> Use a formula to determine which cells to format.
3- for the formula type =Trim(A1)<>A1
4- click on format and pick a fill color and click Ok.
5- Copy cell A1, then highlight the whole bind::esri:fieldAlias column and then Paste Special --> formats.
This will highlight all the extra spaces, then you can delete them in both places.

Regards,

Nabaz

Re: Fields not found in the feature service: 0

Mikaila — Tue, 22 Nov 2022 15:39:40 GMT

Hi Barbara, I am having the same issue, with many forms that report to a single feature service.

Will you please update this thread when the issue is resolved? I am downgrading to 3.14 until this issue is resolved. Thanks!

Re: Fields not found in the feature service: 0

BarbaraWebster1 — Tue, 22 Nov 2022 18:02:19 GMT

A fix for this will be included in the Survey123 3.16 December update, which is currently planned to be released on December 6.

The fix can be tested in the most recent Connect release candidate build, which is available in the Early Adopter Community.

@EddyClark @sth_eagle @MadisonCounty1 @JenniferAcunto @JasonJordan00 @ErikHerbergMETC @ctgb_Caleb_Smith @Nabaz @Mikaila

Re: Fields not found in the feature service: 0

BrittanyBurson — Fri, 25 Nov 2022 22:25:25 GMT

Thanks everyone for posting. I am getting this error, looking forward to the fix.

Re: Fields not found in the feature service: 0

TedChapin — Fri, 02 Dec 2022 19:39:48 GMT

Be aware the proposed fix to put the field alias in the bind::esri:fieldAlias column doesn't work if you have a repeat count field. There is no explicit field for this in the xls form. You have to change the alias of the feature layer. In my case this was unfortunate because I had a view on that layer that I had to remove so I could update the field alias.