|
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
|
2035
|
|
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
|
1415
|
|
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
|
1297
|
|
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
|
2017
|
|
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
|
1272
|
|
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
|
1115
|
|
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
|
1119
|
|
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
|
813
|
|
POST
|
I don't see any way of pulling the access token from Survey123, and even if it was public data I don't see a way to set a message body for a request so I don't see a way to smuggle an update into a pulldata call. Even if you could, would you want your data to be updated at arbitrary points in the form's lifecycle instead of through a defined webhook? No matter how you slice it, trying to update arbitrary layers from a form is a bad move.
... View more
03-06-2025
09:17 AM
|
1
|
0
|
1718
|
|
IDEA
|
It looks like this is either Field Maps or the underlying system libraries localizing "West" to "Oeste" which is too confusing to Google Maps. A "fun" example of what happens when you don't test your alternate locales properly and a very good reason to switch to decimal degrees for display. Although my EN locale machine can't pass those coordinates with comma point decimal formatting so this might be a larger issue with Google Maps.
... View more
03-06-2025
09:06 AM
|
0
|
0
|
1135
|
|
POST
|
As you probably guessed, you can pull data by passing the barcode data into a pulldata("@layer") function and working with the results. To my knowledge there's no documented way to update another layer using a Survey123 form without looking into webhooks.
... View more
03-06-2025
08:52 AM
|
0
|
2
|
1728
|
|
POST
|
Instead of running multiple calls to add_to_definition does doing every field in the fields_to_add_list list work better? I.e.: feature_layer.manager.add_to_definition({"fields": fields_to_add_list})
... View more
03-05-2025
04:51 PM
|
0
|
2
|
2324
|
|
POST
|
If your Org has access to the Enterprise installation files you can see if you can spin up a minimal deployment as a "development" system (i.e. no license costs) and dump your data in there. That way you can see exactly what the storage space will be, or at least very close given the minor changes between 11.4 and the current Online build.
... View more
02-28-2025
02:33 PM
|
0
|
0
|
2478
|
|
POST
|
If your data is one feature per room and every room has a floor number attribute, you don't need to process it any further. Use Export Table (right-click the layer, then Data → Export Table) to dump everything to a CSV, then you can open that in the spreadsheet tool of your choice and pivot the data into the proper shape. Alternatively you can use tools like Summary Statistics or Pivot Table to aggregate your data before you export it. If this isn't suitable you'll have to post a minimal excerpt of your data so we can see what the structure is and suggest the proper tools.
... View more
02-28-2025
02:18 PM
|
0
|
1
|
2127
|
|
POST
|
Unless something's changed in the past few versions, the "Point", "Polyline" etc. classes are still in there and work just like the combined classes in ArcMap.
... View more
02-27-2025
02:33 PM
|
0
|
0
|
2747
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 3 hours ago | |
| 1 | 4 hours ago | |
| 2 | Friday | |
| 1 | a week ago | |
| 1 | 05-24-2023 11:47 AM |
| Online Status |
Online
|
| Date Last Visited |
2 hours ago
|