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; } } }

When I set the FieldType column to null, there is still a field created, it is just blank with no data.

BrandonA_CDPH

I saw a blog post recently on setting thebind::esri:fieldType to null. My understanding is that this allows for questions that are on the survey, but not recorded to the database (in my case, it is a set of validation questions that tell whether or not to proceed).

When I set the bind::esri:fieldType to null, it still creates a field in the responses collected by the form, except this field is always blank. Is there a way to not have the field added at all, that way there will not be an extra column that is always blank? I'm trying to line up to an existing data scheme and it's throwing things off.

Thanks!

Find more posts tagged with

Accepted answers

BrandonA_CDPH

That seems to have solved the problem. Had to copy and paste the XLSForm into a brand new form and start all over. Thank you.

All comments

BrandonArmstrong

Hi Brandon,

You are correct in your assumption that setting the bind::esri:fieldType to null should prevent the field from being created in the database, while allowing for it to be seen in the form. Can you please share your XLSForm and provide details as to the field which is unexpectedly showing?

Thanks,

Brandon

BrandonA_CDPH

Hello Brandon -

Nice name! 🙂

Attached is a portion of the XLS Form document I am using. I am trying to use the null feature for lines 3-6 (PrePack, Refrigerated, ShelfStable) and line 17-19 (PkgSizeOz, PkgNum, SampleSize6). I want to use the first set as criteria to allow the user to continue the form. The second set are collected to ensure a sufficient sample size.

Just as a note, I was using the "hidden" field type, then having the end user remove those columns before transferring to our other data scheme, but that is cumbersome and the data isn't really needed once the criteria are met.

Also, if anyone sees other improvements, please let me know. I'm fairly new to Survey123, so I am definitely open to suggestions.

Block Grant 18-19 BETA 2.xlsx

BrandonArmstrong

Hi Brandon, nice name indeed!

After creating a survey based off of the attached XLSForm and submitting a few surveys using the field app, I do not see any of the fields that you've set to null in the resulting feature service. Are you stating that the fields that you listed (PrePack, Refrigerated, ShelfStable, PkgSizeOz, PkgNum, SampleSize6) have been created?

If so, where are you viewing the data? (Survey123 website or ArcGIS Online)?

BrandonA_CDPH

Yes, they are created and visible both on Survey123 site and ArcGIS Online portal. When I download the Excel table, they are also there with no data in any of the rows. Here's a screen shot of the fields that should be missing from the feature service Screen shot of backend XLS form spreadsheet with null fields highlighted. and one of the results when I submit an entry as viewed from Survey123 website.

Screen shot of Survey123 Results as viewed on teh Survey123 website

Thank you for your help.

Clip_313.jpg

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.