nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Publishing from 123 Connect creates hosted table, not feature layer

VickiG

Hello:

I created a copy of an existing (working!) survey in 123 Connect and made some modifications requested by users. I published to my AGOL account with no errors, but I only have a hosted table with the survey name, not a feature layer. I do have a geopoint question set to null in the survey.

I was able to download the survey to a device and create a record, but when trying to send/upload...the app hangs on "Getting Service Information" and does not upload the record.

Seems like I need a feature layer as in all my previous surveys to make this new survey work. I am not sure why I got "hosted table" when I published this time. My changes were small, moving one field, adding a photo field, and adding a couple items to choices list.

Any help on why this is happening or if I need to do something to convert to a feature layer would be greatly appreciated.

Thanks

Vicki

Find more posts tagged with

Accepted answers

RobertAnderson3

Hey @VickiG and @abureaux

I think I've come across some more information on this one, I've been trying to figure out why some of my surveys have such a tough time loading records into the "form view" on the Survey123 website, and noticed that the _results views created by sharing in the Collaboration tab on the Survey123 website contain an extra table (duplicate of the main table) Results View Contains Additional Tables compared t... - Esri Community

In going through this with Esri Support, they finally connected the addtional tables to BUG-000147659 for ArcGIS Online (esri.com)

It seems that if you have a geopoint question with bind::esri:fieldType = null it will create a hosted table instead of a hosted feature layer, which sounds like it may contribute to my additional tables and loading issues. Did you encounter any issues like this when you had the hosted table, or did you get that far with it?

All comments

VickiG

Hi Robert:

Just saw this response, as I am back into S123Connect world after a couple of months on some other things.

I never had the duplicate table problem, but I can confirm that I removed "null" from the geopoint question, which was really just to contain a reference map, no point data was being collected from that question, and republished. Now I got a feature layer not a table.

Not sure why the null was there in the first place, maybe because I didn't want data collected there?

But publishing to feature layer is working fine...for now (*evil laugh from S123Connect*)

Thanks for your input on this.

Vicki

RobertAnderson3

Hey @VickiG and @abureaux

In going through this with Esri Support, they finally connected the addtional tables to BUG-000147659 for ArcGIS Online (esri.com)

VickiG

Hello again,

Just to follow up on this...I did correct the issue, but still not really sure why it happened in the first place. I think the template for S123Connect I was using was somehow corrupted along the way. Today I went back and found a template Version 3.16, known working (publishing Feature Layer, not hosted table).

I created a new survey from that xslx file in the "New Survey" workflow within S123C, no changes in questions, published fine to Feature Layer. I tried again from the beginning, New Survey, same template, made changes, published fine to FL. Next iteration was to make New Survey, no changes, update XLS template to 3.19, publish, all OK...made a FL. Last iteration was make New Survey from 3.16 template version, make changes, update to 3.19, save, and publish. Success!

I did have a phone call with ESRI support as well, we stepped through the workflow from my last iteration, same successful result. They didn't really have a definitive answer either.

So I guess the take away here is hang on to your old working survey template in a file somewhere!

Thanks again for all the suggestions. The help from this message board is the only reason I haven't run screaming from the office on many days! 🙂

FeatureLayerCreated.JPG

VickiG

Sure, here are the two versions:

The 28Feb24 is the original survey, still working through AGOL, with feature layer, I haven't republished or updated this survey since early March...terrified it will break! 😉

The modified one is the Jun2024, I added an observer, moved the "Time RS Seen" question down in the table and added a photo question near the end.

My work flow was in S123 Connect, "create new survey from file", pulled in the Back28Feb, renamed, made the changes in the xslx form, copied media files from old folder, set the options to the screenshot and tried to publish.

Don't be too horrified at the survey set-up, I'm sure it is not very elegant. I had to modify a legacy survey to S123Connect, knowing nothing about S123 Connect! I'm surprised it ever worked at all! 😉

Thanks so much for your help!

Vicki

p.s. I asked our IT person to put a ticket in with ESRI on this as well...hope they have an answer!

UA_RedSQ_Survey_Back28Feb24.xlsx

UA_RedSQ_Survey_Jun2024.xlsx

S123C_options.JPG

abureaux

Is it possible to attach your XLSX? I am curious if I'd have the same issue when publishing.

VickiG

Hello, just double checked, I do have the the most recent version.

I think I updated not too long before I started to create/copy the new survey.

Still trying to figure this out...any ideas are appreciated!

Thanks!

Vicki

abureaux

I don't believe that has been asked yet, but what version of Connect are you running? Current version is 3.19.116

(Note that the MS Store version of Connect auto-updates)

VickiG

Hi all:

Thanks for the info and suggestions, I tried/checked the items you all thought of, no luck so far. I did have the "create web form" checked. Tried a republish, no luck. Removed the geopoint question, save, republish, no luck. Not sure what happened here. The original version was working fine a couple months ago.

I'm going just tell the users, hey, no more changes ever! 😉

I'll report back if I figure something out.

Thanks again all!

VickiG

Hi, thanks for your reply!

This survey was copied from an old working one, slight changes made then published...making the hosted table.

I do have a geopoint question (I think I had to have one?), but set to null bind::esri:fieldType, the same as the old survey. But the actual survey doesn't collect a location question. The points we are surveying are all known and mapped already.

I checked permissions, thought right now I am the owner and only member of the test group.

So not sure what is happening, I tried to send again from the app, but get the same churning on "Getting Service Information", nothing gets sent.

So I'll keep playing around and report back if I figure something out.

Thanks again

abureaux

I guess the one thing I see that is super annoying is that some surveys, when they republish, create duplicate Feature Layers. So I've definitely gotten more than three items before, but never less. (Your post reminded me I have one of these I need to go clean up!)

RobertAnderson3

I always get 3 items as well, the map, the form and then a feature layer or a table. Then when I've enabled editing and gotten the _results view, it's a table as well (although I did just see one survey I have where the main level is a table and the _results is a layer... which makes even less sense)

abureaux

Odd. I always get all three layers, irrespective of survey contents. (Enterprise)

For example, this only has one question:

If I ever saw anything less than this I'd consider it a mis-publish, and delete and try again.

EDIT. Out of curiosity, have you ever changed this setting? I honestly forget it's there since I always leave it turned on...

RobertAnderson3

I have noticed getting some Survey123 forms publishing with a table instead of a feature layer as well, I'm curious what makes the decision between creating a table or feature layer, if anyone has any insight I would love to hear it!

The one's I have had do this do not have a geopoint so I assumed it was that. Is your geopoint calculated to null or set to a null bind::esri:fieldType? And was it null in the survey that you copied as well/how old was that initial survey?

I also have not had any issues submitting to the surveys that are stored as a table, double check your permissions on the new survey for who's allowed to submit/edit it maybe? Or are you using the same account that published it to try and submit?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.