Is it possible to apply a definition query in ArcGIS Pro that behaves in the same was as the "Filter" on the Survey 123 website.
On the website i can filter by any of the attributes and it will automatically apply that filter across the related tables and feature classes that have been created with repeats inside the survey.
In ArcGIS Pro, when applying the same logic by adding a definition query to the "parent" survey, it only filters the records in the parent survey feature class and not the related feature classes.
The only way to then filter the related ones are either by carrying through the information in the parent survey into a hidden field in the survey to allow the same definition query to be applied, or to apply a definition query to the "parent global ID field", which can get quite confusing particularly if you are filtering more than one parent survey. Additionally, I have noticed that the parent global ID fields are a mixture of lower case letters and numbers by default from Survey 123, however if you edit anything using Pro, the globalID/ParentGlobalID suddenly becomes uppercase letters and number (albeit the same ones) and therefore the definition query fails.
Any insight into how to set up easy filters like in the Survey 123 website would be great
Does following the relates work for you? It would be nice though for sure. I always pass my keys down to every related table though for sure as it helps a lot in QA later. I also pass the project name and state to every single table. Helps a lot in dashboards, etc.
On the GlobalID case issue I have been posting this for awhile now. Kinda crazy this got into production. I really wish the Esri teams would coordinate on this stuff.
I reported it but checked my email and never for a bug number back. Am checking on that.
https://community.esri.com/t5/arcgis-pro-questions/globalid-inconsistent-display/td-p/291405
The worst part about this is it will break your relationship when it changes case!
Hi Doug,
Thanks for your reply, I've been doing as you have, passing through the fields I need such as project name and number through my repeats into hidden fields and just using the parent one in the calculation field. Its a solution but obviously not ideal as you need to add the definition query to each layer/repeat.
Completely agree on the GlobalID stuff, surprised it made it through as you say it breaks the relationships, and any queries you may build on that attribute, and as they are read-only fields you cant even use lower(GlobalID) etc to force it back to lower case
Hopefully its something that gets sorted soon
Cheers
Got it now BUG-000146406: Inconsistent letter cases for the Global ID values between ArcGIS Desktop and ArcGIS Online products.