|
POST
|
Ah, that makes sense. Add a hidden geopoint to your form to capture the user's location, then use the getRecordAt or getValueAt modes of pulldata to select the park that way (the docs have more details).
... View more
03-19-2025
12:57 PM
|
1
|
2
|
2245
|
|
POST
|
At first glance your form looks configured correctly: the user picks a park from the list of possible parks and the pulldata call grabs the exact geometry of that park. Are you trying to do something else? It's not clear what the issue is from how you've written your question.
... View more
03-19-2025
12:46 PM
|
0
|
4
|
2249
|
|
POST
|
Assuming you save the device ID in the results, you can pull data from the previously submitted surveys using the pulldata function to see if the device has a survey logged. In theory you can pull the entire previous survey into a set of fields, then use another set of fields to coalesce that with the current answers to get the final question set, but this will make the survey much more difficult to maintain so you'll have to weigh the pros and cons.
... View more
03-13-2025
03:22 PM
|
1
|
0
|
1038
|
|
POST
|
What is the profiler showing as your hot spots? If the lion's share of the time is spent in rendering-related code you might be out of luck if you want an immediate render using world-space data. Building a full list of graphics elements before adding them to the overlay might help here; you can even try building them in a thread or async task that you cancel on each event to avoid blasting graphics at the map when the user makes quick adjustments. If the bottleneck is constructing the zigzags themselves, two things you can try are: Hoist as many reusable heap-allocated objects out of the function as possible, the less garbage your zigzags accumulate the better. Do all calculations in the map's current coordinate system and try to use the GeometryEngine extension methods to do as much of the math as possible to avoid coordinate errors. This eliminates any reprojection between your graphics and the map.
... View more
03-13-2025
10:54 AM
|
1
|
0
|
3226
|
|
POST
|
It's a bit tricky to see what's going on without proper code formatting but it looks like you're rebuilding the IS layer every loop. Does the tool work correctly if you give each layer a new name every loop? Alternatively, can you hoist the layer out of the loop and build it without an extent? Or do you need to define a layer with a limited extent to ensure the clip works?
... View more
03-13-2025
10:29 AM
|
0
|
0
|
978
|
|
POST
|
If the incoming data f isn't already a number, you can triage null values like so: Iif(IsEmpty(f), null, Number(f)).
... View more
03-13-2025
08:05 AM
|
0
|
1
|
2592
|
|
POST
|
EGDBs group versioned edits into "states", where the state is chosen based on things like creating new versions, adding a replica etc. If you have something that's expecting to talk to a specific state then that state can't be removed, which means the related edits have to stay in the delta tables. I don't know exactly how things work but if you have no child versions, no replicas and no other connections to the database then a compress should clear out the delta tables. Unless a state entry is "stuck" in the system tables, that's what support can walk you through.
... View more
03-12-2025
02:07 PM
|
0
|
0
|
1989
|
|
POST
|
Record compression (how much is in the business table vs the A/D delta tables) is orthogonal from how many active versions you have. It's possible for a table with only 1 version to still have data in the delta tables because the SDE tables have determined some of those edits belong to an active "state" and shouldn't be relocated. Start by ensuring there are no active connections to the database aside from the one you're running the Compress tool from. If you still have data in the delta tables then contact your support rep and work with them to clear out the stuck states, this'll involve making direct edits to SDE tables and runs the risk of EGDB corruption but there is a process to do this safely.
... View more
03-12-2025
11:03 AM
|
0
|
2
|
2019
|
|
POST
|
To add on to this, if you need to pull one related record to update another, you can try something like this example to update another record.
... View more
03-11-2025
02:43 PM
|
1
|
0
|
1408
|
|
POST
|
Pop open the file geodatabase folder in explorer, find every .lock file and delete them. Any active locks will trigger the usual Windows error, from there you can use a tool like the File Locksmith in Windows PowerTools to figure out what's holding the lock and then stop that program to safely release it.
... View more
03-07-2025
12:56 PM
|
1
|
0
|
1290
|
|
POST
|
I ported your code to a standard toolbox tool (see attached) and everything ran smoothly. Some notes: There's no Tool class anymore, just a standard script tool layout. Wrapping your code in that class was almost certainly the issue as the script tool simply defined the class and then immediately finished. If you want to use that style, you'll either have to switch to a Python Toolbox or add something like this to the bottom: Tool().execute(). Your original script didn't check if the topology already had the feature class added, this has been fixed. Your tool had no return value which could cause issues if it was combined with other tools in Modelbuilder. I chose to return the feature dataset but the choice is up to you. Avoid tab indents for Python scripts, that ship sailed a decade ago and most Python tools will create a mixed whitespace nightmare during edits. Luckily it's very easy to bulk convert tabs to the standard 4 space indents and then change the defaults going forward.
... View more
03-06-2025
04:51 PM
|
1
|
1
|
2011
|
|
BLOG
|
Heads up, the link goes to the prior update instead of the current one. As for the update, I'm curious if bulk editing is still on pace for June 2025. The Editor app now has a limited version of it, I'm hoping the team can leverage this to get this over the line in time for Enterprise 11.5.
... View more
03-06-2025
03:55 PM
|
1
|
0
|
1269
|
|
POST
|
I'd say it's worth exporting the model to Python just to see how Pro translates it. If you're on 3.4 you might get lucky if you throw that script into a modern editor and go red squiggly hunting. If I was in your shoes my long term plan would be to port the model by hand and apply as many Python-only optimizations as I could (e.g. looping over feature class names for export, using cursors and lookup tables where possible etc. etc.) but that's a daunting task for a model that size so beating it into a working state would be my #1 priority.
... View more
03-06-2025
11:38 AM
|
0
|
0
|
1103
|
|
POST
|
Copy-paste the model to another toolbox, pop it open, delete some tools from the tail, run it, and repeat with greater and greater cuts until the errors vanish. Once it's working you can make another copy, trim one tool less and see if that triggers an error. You can then build a model that runs that tool with more and more preceding tools until the error triggers again. This is exactly as tedious as it sounds but these excisions are the best way to solve the issue.
... View more
03-06-2025
11:04 AM
|
1
|
2
|
1107
|
|
POST
|
Using the pulldata("@layer") function you can get the count of how many previous surveys match the provided name and/or e-mail. You can then check if that count is greater than 0 in various expressions to control the survey flow. Make sure you test this before you promise anything, there might be issues pulling from the layer depending on how you've configured your data, if you're using the web forms etc. etc.
... View more
03-06-2025
09:24 AM
|
0
|
0
|
808
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Tuesday | |
| 1 | 05-24-2023 11:47 AM | |
| 2 | 04-09-2026 11:36 AM | |
| 1 | 09-08-2023 10:07 AM | |
| 3 | 03-26-2026 08:11 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|