Select to view content in your preferred language

123 Connect, locations not plotting

140
2
02-14-2025 07:22 AM
JayHodny
Frequent Contributor

Hello, I am using Survey123 Connect in a Dashboard to record refuse cart transactions.  We employ this GIS approach on several other programs. The Connect form uses the 'pulldata' function against a feature service that has the cart location information.  This is quite convenient, and we don't have to rely on .csv files.  We enter an address in a drop-down question in the Survey form and select the address as the choices narrow.  This triggers an autocomplete of the parcel number which provides our location.  If the parcel number does not appear in the form, the cart record is still created, but no parcel number or related globalid are written to the table, and the point is not plotted on the map. 

When the address is selected but no parcel number appears.

JayHodny_0-1739546171967.png 

Results in no parcel number or rel global id in survey table, and no point on the map.

JayHodny_1-1739546214023.png

What we usually see when entering an address, parcel number is populated in the form and in the table, along with the rel globalid.

JayHodny_2-1739546262472.png

Generally, we can delete the 123 record, try again, and we have success.  I don't know why this happens occasionally.  Overall, the solution has worked fine for well over a year with these occasional glitches.  Back in December, and now today, this "missing" point issue instead persisted.  Deleting the record and trying again isn't working.  I have cleared my browser cache, stopped and restarted our portal, server and data store services twice.  Rebooted my laptop.  I am going to republish the 123 service again and see if this corrects the issue.  Unfortunately, we don't recall how the issue was resolved back in December, we did not document the resolution well or maybe it simply went away. 

Any insight/help would be greatly appreciated.  Kind regards, Jay

0 Kudos
2 Replies
DougBrowning
MVP Esteemed Contributor

Is the pulldata in any kind of a if statement or other statement?  If so that is a known issue.  It can also fire before the field you are picking at times.  Setting a relevant can help here.

You really need to post the lines affected or a form in order to troubleshoot at all.

JayHodny
Frequent Contributor

Hi Doug,

Thanks for the quick reply.  Let me check, I haven't looked at the XLS code in awhile as things were working.

I never sure what to share and to what depth.  I can send you the form via secure email if you want to take a look.  Regards, Jay

0 Kudos