Latest Contributions by SFM_TravisBott

Interesting. All of the linked discussion is round ExB applications hosted on Enterprise. Mine is AGOL., using no Developer Edition applications. Is there reason to suspect it still applies. ... View more

It's a bug. If there's a geopoint question in a nested repeat hidden by a relevant condition it still sends a ghost record.  I posted my workaround here: https://community.esri.com/t5/arcgis-survey123-questions/blank-rows-in-hidden-repeat/m-p/1644553#M63905 ... View more

I'll reply to my own post here in case anyone comes looking since I found a workaround that seems to function in 3.20.63. In my case I have nested photopoint repeat. There's a geopoint question, an image question, and a few others. The repeat has a relevant condition on a proceeding question, 'NeedPhotos' (${NeedPhotos} = 'Yes'). The NeedPhotos question is itself subject to a calculation...if a previous question (PositiveImpact_YN) is set to 'Yes' then the NeedPhotos question is automatically set to 'Yes' and photos are enforced. I noticed this behavior: If in the course of the survey PositiveImpact_YN is set to 'No', the photo repeat does not appear (desired behavior) but it sends a ghost record (undesirable behavior). However, if I set PostiveImpact_YN to 'Yes' (photo repeat appear), then back to 'No' (photo repeat disappears), then it doesn't submit a ghost record. It's like the survey needed some positive affirmation do the right thing, and it fires appropriately and strips out the photo.  For my case I changed the NeedPhotos calculation and added a calculation in the 'Visible' column...so the user can't see it but behind the scene the 'NeedPhotos' gets defaulted to yes, but is invisible, and then the above chains of calculations from PositieImpact_YN will push it back to 'No', and the ghost record gets killed. ... View more

@NicoleJohnson Well shoot dang! You're right that I didn't read carefully - you specifically mention joined views in your post. I used your technique and it worked perfectly. Previously I've done it by going through the REST endpoint for the parent layer, and I had never come at it from the view itself. Seems to have worked fine. Thank you! An additional edit - Below is from Esri support services: It was a pleasure speaking with you earlier, and I understand you need assistance with joined view layers in ArcGIS Online. I have included a brief recap of what we have discussed during our screen share session: You created a joined view layer using a left join in ArcGIS Online and successfully published the view. Upon attempting to edit data via the Data tab, you found that there was no option to edit fields. This is expected behavior, as editing is disabled by default for joined view layers in ArcGIS Online. Additionally, fields from the joined (right) layer are read-only by design and cannot be edited. You attempted to work around this by accessing the REST endpoint of the view layer. You used the Update Definition operation to change sourceSchemaChangesAllowed from false to true. I just reviewed the workaround on my end, and I wanted to share that updating the service definition in this way is not a recommended approach. While it may be technically possible to make this change, there are several important risks and limitations to consider: Joined views are not designed for editing, and forcing edits can lead to unexpected behavior, such as broken relationships or schema mismatches. In ArcGIS Online, joined hosted feature layer views can prevent schema modification of the underlying feature layers. This means you can't add or remove fields, or alter domains, in the source layers while the view exists. This ensures data integrity If issues arise as a result of this modification, technical support may be limited, as the workaround involves changing internal service properties that are not officially supported. Alternative Suggestion: If schema changes are required, a safer approach would be to temporarily delete the joined view, apply the necessary schema updates to the source layers, and then recreate the join view afterward. Please let me know if you'd like help exploring this option or if you have any further questions. A note to Esri - Consider a) providing a warning when creating a joined view that your schema will be locked; b) make it possible to update a joined view. I bet you could if you really put your mind to it.   ... View more

@gis_KIWI4 This is not correct. The option to add fields and domains is not available with a joined view. I will edit my post to provide some emphasis. ... View more

@Tiff I think you're the only one here to read and understood the post. There are options in the GUI to update fields for traditional views. Joined views lock everything up considerably worse. ... View more

Holy moley it's be six years and this still isn't resolved: https://support.esri.com/en-us/bug/if-a-relevant-field-is-configured-on-a-repeat-to-only-s-bug-000123943 I sure hope somebody can suggest a workaround. ... View more

I came here hoping to find something different. I configured my survey in the way you describe and I'm still getting ghost records in a nested repeat. https://community.esri.com/t5/arcgis-survey123-questions/ghost-repeat-records-being-written-even-though/td-p/1642098 ... View more

@AlixVezina Thank you following up. This is when this forum is at its best. As users we're often confronted with situations where we're just not sure what's possible, as the products move fast and the documentation doesn't keep up. So it's nice when someone from Esri can pop in and provide a "yeah, don't even bother it's not possible" kind of answer before we waste more time pursuing it. On another note, it would be wonderful if this was different! Seems a shame when settings that you can specify do not actually get honored. ... View more

@VenkataKondepati Thanks for the detailed response. I can certainly look at other ways to get a little more creative with editing. Our users have a decent out, in that all of the data collected is generated through Survey123 and the pop-up contains a URL parameter so they can edit their data in Survey. However, there are lots of small edits that might take place within the workflow, and the functionality of the List Widget + Editor is nice, and much preferred, so long as it works. Building the app on a View, which doesn't allow geometry editing at all (and would therefore disallow adding a new feature), might work, but I've been moving away from Views as any updates get complicated. ... View more

@AlixVezina Thank you for the note. I am aware of that behavior (which, in my humble opinion, absolutely shouldn't exist), as I've been bitten by it before. I have verified the behavior across different accounts, much the same as my users will access it. ... View more