Latest Contributions by SFM_TravisBott

‎11-04-2025

Mine have spontaneously resolved and begun running as normal again. I'd consider this resolved, though I'd like someone to tell me what happened.

‎10-31-2025

New issues since recent AGOL update: all of my scheduled notebooks fails with the message below: { "error": { "code": 90031, "message": "Invalid value for executionTimeoutInMinutes for notebook job run.", "messageCode": "NBO_90031", "details": [] } } All of them were set to the maximum allowable limit (1440 minutes, which is 24 hours), and they worked like this for a long time. I since backed them off to 1000, just to be sure, as none of them take remotely that long. Same issue. So what's the deal? All scripts run fine when executed manually. All are in runtime 10 or 11. How do I get the task to accept a parameter that is entirely within the specified limits?

‎10-14-2025

I have a feature service with three layers and a table. Layer [0] is 1:m with layer [1] and table [0]. Layer [1] is 1:m with layer [2]. The parent layer, layer [0], has a status field (ReportStatus). I have a view configured (for public consumption), with the only filter being on the parent layer (Report Status - 'Complete-Approved'). This, for a while, has successfully worked in automatically querying down related records downstream. But now it does not. We have records recently being created which are going past and appearing in the child table as 'orphans.' I have checked and re-checked - the child records are related appropriately, their parent definitely does not meet the criteria to appear (and it doesn't, which is correct). I have removed the filter, saved the view, and then re-applied it, but the same records trickle in inappropriately. Can anyone offer guidance? I have a workaround in mind, where I can add a field to the child tables and use a script to push the status downstream, putting filters there as well....but I'd rather the thing just work as it was designed, which it did just fine not too long ago. Disregard: I was mistaken, no filtering was taking place originally on the child later. So now I know I need to add fields to get the status field to carry over. So, Esri: you should allow the option to a) allow parent layers in views to filter child layers; b) allow me to delete posts?

‎10-08-2025

@IngridHogle Can you elaborate on your first Arcade issue? Maybe provide an example? I am having a similar situation. Post update I had two issues, both exclusive to Field Maps (all worked fine the web maps). The first was with editing the form in the Field Maps designer...I got generic error messages saying it couldn't be saved because there as a problem. I removed all of the fields from a group a and re-added them and that fixed it. My second issue, which your post might speak to, involves an if/else statement to declare a variable in a pop-up. It uses html and works just fine in the web map as-written, but with certain templates it shows an error for the pop-up in Field Maps. It's generic (ArcGIS.InvalidCallError error 1), but I've narrowed it down to the logic around declaring a variable.

‎08-27-2025

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.

‎08-27-2025

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

‎08-27-2025

Yessir. The problem turned out to be I was not storing the URL that was used for the queries, so when an edited survey was opened it didn't have anything to reference for where to look. And because of the firing rules for a survey in edit mode it doesn't re-calculate for fear of overwriting an existing value, even if calculation mode is set to always. So the solution was to store the URL as an attribute so an edited survey could reference it.

‎08-26-2025

I'm having some issues with permissions with the Experience Builder Editor Widget. A few weeks ago I made this post, which turned out to be me just being a bit of a dingbat...but myself and some testers have noticed some erratic behavior: editing permission changes periodically. A user can navigate to the application with an account that has permissions, open the Editor widget, and be told the form is read-only. They can re-open the application a short time later and receive no such warning. As I am the only editor of the application I can confirm no changes have been made to anything related to the application within these time windows. Has anyone else out there experienced similar behavior, or is this gremlins behavior? Clearing chache and using different browsers does not seem to be related. It happens more often to accounts outside of the org, though they have all of the necessary permissions to view the app/map/data.

‎08-21-2025

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.

‎08-20-2025

@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.

‎08-20-2025

@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.

‎08-20-2025

@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.

‎08-19-2025

I am wondering if anyone here has guidance on best practices for updating schemas/domains for hosted feature services with views. This is the kind of thing that seems to change constantly as the platform shifts. Context: I have a feature service that has two 'traditional' views and one joined view. In my case I'd just like to add one additional value to a single field's domain. What's the the 'correct' way to do this these days? I can think of two methods: Kill the views and do it manually. As there are several maps/apps that depend on this particular item, I could delete the views, update the schema, and re-create them, then using the python api point the layers in the map to the new views (pretty big PITA considering the scale of the change to be made) Make changes through the REST endpoint, either manually through the GUI or the API. Less of a pain, but the risk of corrupting the service (and then creating way more problems than the above) is greater than zero. Any thoughts would be appreciated. Edit: the joined view is the issue here. You have options through the GUI with traditional views but not with joined views.

‎08-14-2025

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.

‎08-14-2025

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

Online Status	Offline
Date Last Visited	‎11-06-2025 12:24 PM

My Ideas

Latest Contributions by SFM_TravisBott

Re: ArcGIS Notebook on AGOL: nvalid value for executionTimeoutInMinutes for notebook job run

ArcGIS Notebook on AGOL: nvalid value for executionTimeoutInMinutes for notebook job run

Feature service view with related records not filtering from parent

Re: Arcade referencing original feature broken after update

Re: Experience Builder editor widget permissions erratic

Re: Ghost repeat records being written even though relevant condition not met

Re: Best way to open and edit existing surveys in web app with URL parameter

Experience Builder editor widget permissions erratic

Re: Blank rows in 'hidden' repeat

Re: Best practice for updating schema/domains for feature services with views?

Re: Best practice for updating schema/domains for feature services with views?

Re: Best practice for updating schema/domains for feature services with views?

Best practice for updating schema/domains for feature services with views?

Re: Blank rows in 'hidden' repeat

Re: Nested repeat creating blank record when paging backwards through repeats.

ArcGIS Notebook on AGOL: nvalid value for executio...

Re: Blank rows in 'hidden' repeat

Re: Blank rows in 'hidden' repeat

Re: Experience Builder Editor not honoring setting...

Re: Experience Builder Editor not honoring setting...

Wildfire Response GIS