Fields not found in the feature service: 0

[EddyClark]

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://...

[GregoryLiggett]

Is there any update on this issue? The field Alias fix is not working for me.

[EddyClark]

Check that you've updated to 3.16+

[JasonJordan00]

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.

[BarbaraWebster1]

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

[ErikHerbergMETC]

@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.

[ctgb_Caleb_Smith]

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?

[BarbaraWebster1]

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

[ctgb_Caleb_Smith]

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

Thanks,

Caleb Smith

[BarbaraWebster1]

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

[Nabaz]

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