POST
|
Python treats null values as none. And python can't add to nothing. Attribute1 = null Attribute2 = 5 Current State: Attribute1 + Attribute1 = none + 5 = null To handle Nulls: Use or include a default value (!Attribute1! or 0) + (!Attribute2! or 0) = 0 + 5 = 5 Or use arcade: $feature.Attribute1 + $feature.Attribute2 = null + 5 = 5
... View more
08-06-2025
03:09 PM
|
0
|
0
|
131
|
POST
|
I am currently experiencing the same issue. Guess I will try again in a few hours
... View more
04-04-2025
11:58 AM
|
0
|
1
|
1515
|
POST
|
I'm experiencing random glitches with our department's legacy model. Specifically, it's generating errors at points where it previously functioned correctly. I am using Pro 3.2.2, has there been a recent update I should be aware of? The current workaround involves replacing the malfunctioning tool with a new instance, configuring it identically, reconnecting the inputs and outputs, and then disconnecting the old tool before rerunning the model. The tools that appear to be causing these issues are 'Copy Features', 'Select', 'Dissolve', 'Buffer', 'Spatial Join', and 'Merge'. Does anyone know how to update the model without having to rebuild the tools? In the below example, I added a new Spatial Join configured it exactly as before, repointed the connections and the model finishes just fine.
... View more
03-27-2025
04:23 PM
|
1
|
0
|
326
|
POST
|
Try adding a new Calculate Field tool to the model, and replacing the one that is causing the error
... View more
03-27-2025
02:34 PM
|
0
|
0
|
489
|
POST
|
I just had the same thing happen to me. One of the toolboxes, just died. Tried to open it in a new project, and no luck
... View more
03-12-2025
08:53 AM
|
0
|
0
|
1472
|
POST
|
@DavidSolari I apricate the tip and will give it a go. While it does sound tedious, it is better than my plan of exporting to python hoping the error continues. And add print prompts to annoyingly track the model.
... View more
03-06-2025
11:21 AM
|
0
|
1
|
464
|
POST
|
I've inherited a model that runs without errors when opened and executed in edit mode. However, when I simply open the model and run it directly, it throws an error. Since it works in edit mode, the usual debugging method of observing what turns red isn't helpful. I'm struggling to pinpoint the source of the error. Is there a way to modify the model, to help me debug the model, and track its flow and narrow down the location of the error? The model itself is huge, and I would rather not have to rebuild it. Based on the limited messages, it appears to be failing in the later third of the model. Any help on how to debug the model would be greatly appreciated.
... View more
03-06-2025
10:49 AM
|
0
|
3
|
472
|
POST
|
I was not, the project lost steam and has been placed on hold
... View more
02-24-2025
12:24 PM
|
0
|
0
|
207
|
IDEA
|
Thank you @LindsayRaabe_FPCWA that did work. It would be a great enhancement to make the Export Features GP use of a generated Output Name a simple drag and drop as we previously could with the now depreciated Feature Class to Feature Class GP tool.
... View more
02-11-2025
08:40 AM
|
0
|
0
|
444
|
POST
|
As there does not seem to be a way to match previous functionality, I have also posted this as an idea. Match previous functionality of Export Features to... - Esri Community
... View more
02-10-2025
02:54 PM
|
1
|
0
|
343
|
POST
|
The new Export Features tool removes a major functionality of the Feature Class to Feature Class. The ability to use a model variable for the Output Name is highly useful to add in a timestamp to the output. I have suggested this idea as an idea Match previous functionality of Export Features to... - Esri Community
... View more
02-10-2025
02:52 PM
|
0
|
0
|
315
|
IDEA
|
Match previous functionality of Export Features to Feature Class to Feature Class. The Feature Class to Feature Class (deprecated) allowed dynamic Output Name using string variables, which was very useful for adding timestamps and differentiating model runs. This model is run approximately every 3-6 months, and being able to have historic data automatically saved is a key component. The Export Features GP tool (replacing Feature Class to Feature Class) no longer allows model variables to be used for Output Name. This eliminates the ability to easily add timestamps to exported feature layer names. While I can manually rename the exported layer, this extra step wasn't needed with the Feature Class to Feature Class tool
... View more
02-10-2025
02:49 PM
|
0
|
3
|
500
|
POST
|
The Feature Class to Feature Class (deprecated) allowed dynamic Output Name using string variables, which was very useful for adding timestamps and differentiating model runs. This model is run approximately every 3-6 months, and being able to have historic data automatically saved is a key component. The Export Features GP tool (replacing Feature Class to Feature Class) no longer allows model variables to be used for Output Name. This eliminates the ability to easily add timestamps to exported feature layer names. While I can manually rename the exported layer, this extra step wasn't needed with the Feature Class to Feature Class tool
... View more
02-10-2025
02:42 PM
|
3
|
1
|
347
|
IDEA
|
Can't believe Table Frame Elements don't have a built in Title option like a Legend does. In order to add a title, I had to add a second Text element, and line them up as best as I could. With a Legend Element you can easily toggle on/off a customizable title
... View more
01-30-2025
03:42 PM
|
0
|
0
|
373
|
Title | Kudos | Posted |
---|---|---|
1 | 04-02-2021 12:12 PM | |
1 | 10-18-2022 11:12 AM | |
1 | 06-13-2023 08:55 AM | |
1 | 05-22-2024 03:26 PM | |
1 | 04-26-2024 01:50 PM |
Online Status |
Offline
|
Date Last Visited |
yesterday
|