|
IDEA
|
@HannesZiegler , great news, thanks for sharing and for getting the functionality fixed/updated.
... View more
3 weeks ago
|
0
|
0
|
84
|
|
IDEA
|
For parameters names that are the same, e.g., mergePolicy and merge_policy, I understand how the difference comes about since Python's best practice for naming variables uses snake case while camel case is the convention with some other languages like C, C++, etc... Where things get dicey for me is when the name itself is different, e.g., description and domain_description. Even if one converts snake case domain_description to camel case domainDescription, they aren't the same name although they refer to the same item. At least if the names were exactly the same and it was just a snake case versus camel case issue, it would be more straightforward to translate. Unfortunately, the discrepancy with handling parameter names propagates down into the accepted literals, which exacerbates the situation.
... View more
4 weeks ago
|
0
|
0
|
237
|
|
IDEA
|
Unfortunately, Python doesn't support parameter name aliases like some other languages because that would allow for a fairly straightforward way to address it.
... View more
4 weeks ago
|
0
|
0
|
245
|
|
POST
|
See BUG-000125894 for ArcGIS Pro, Esri has no plans to address.
... View more
a month ago
|
1
|
0
|
98
|
|
POST
|
I agree about CTE. I suggest you submit an ArcGIS Pro Idea to support using CTE with SQL Server query layers.
... View more
10-31-2025
07:53 AM
|
0
|
0
|
136
|
|
POST
|
Something like the following should work or get you close: tbl = # full path to table or feature class
text_fields = [
field.name
for field
in arcpy.Describe(tbl).fields
if field.type == "String"
]
with arcpy.da.UpdateCursor(tbl, text_fields) as cur:
for row in cur:
row = [
item.upper() if item else None
for item
in row
]
cur.updateRow(row)
... View more
10-22-2025
12:57 PM
|
1
|
0
|
266
|
|
POST
|
One must remember that ArcGIS Server accesses file-based data sources, including network file shares, using its own credentials and not the credentials of the person who ran and published the tool. If the credentials running ArcGIS Server don't have access to the data set location, the tool will fail.
... View more
10-13-2025
02:02 PM
|
0
|
1
|
137
|
|
POST
|
ArcGIS software does not set or determine the collation of data sources. The default collation of most data sources is case sensitive, which you are seeing with the file geodatabase. For RDBMS, SQL Server and MySQL are commonly case insensitive while Oracle, PostgreSQL, and DB2 are commonly case sensitive. Unless you are able to enforce specific collations of data sources, or force how users input data through validation rules or similar, it is best to assume all queries will be case sensitive and adjust your queries accordingly. I am not a JavaScript developer, so I can't say for sure, but I believe SQL UPPER and LOWER functions will work within a definitionExpression.
... View more
10-13-2025
02:00 PM
|
2
|
1
|
278
|
|
IDEA
|
@TanuHoque , thanks for chiming in on this discussion and for considering the idea. @DavidFotheringham1 , thanks for posting the idea and getting the discussion wrong. I am always open to being wrong, even happy at times about it, when it means improvements come quicker than I expected.
... View more
10-07-2025
06:58 AM
|
0
|
0
|
161
|
|
IDEA
|
Although I understand the value of having this functionality dynamic, and I don't think implementing a naive approach to it would be difficult, the fact that spatial operations are so compute intensive makes implementing an efficient means of doing it very challenging. For the example given here, even a naive approach would likely perform fine, but what happens when there are millions of points or the polygon itself has tens of thousands of vertices? In that case simply panning or zooming a basic map would result in the noticeable, if not significant, delay in refreshing the screen. Raising ideas is good, and I think the discussion around them in the community is good for Esri to read, but this is one where I would not hold my breath.
... View more
10-01-2025
06:02 AM
|
0
|
0
|
614
|
|
POST
|
Unfortunately, no, this is a major shortcoming of Esri's Named User licensing model. My personal belief is that the shortcoming is purposeful, i.e., they could have addressed it by now if they wanted to address it. So, organizations are left to come up with their own myriad of automations to address time-based Named User licensing.
... View more
10-01-2025
05:37 AM
|
0
|
0
|
172
|
|
POST
|
More information would have to be shared before community members could provide anything beyond anecdote and links to general documentation. For example, is this a hosted feature service or a referenced one? If referenced, what is the back-end data store and what style of versioning is being used with the data? Depending on the answers to these questions, there are even more questions.
... View more
09-29-2025
07:50 AM
|
0
|
1
|
526
|
|
POST
|
Esri will fully retire ArcGIS Pro 3.1.x in 6 months (April, 2026). If you upgrade to a recent version now, these questions/issues are moot.
... View more
09-29-2025
07:42 AM
|
0
|
0
|
407
|
|
POST
|
Are the data sources stored locally on your computer or a shared network drive?
... View more
09-25-2025
08:36 AM
|
0
|
0
|
142
|
|
POST
|
When asking about data management-related issues, it is helpful to state what the back-end data source is because whether something is a shape file vs file geodatabase vs enterprise geodatabase can make a difference.
... View more
09-24-2025
07:10 AM
|
0
|
0
|
420
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a month ago | |
| 1 | 10-22-2025 12:57 PM | |
| 2 | 10-13-2025 02:00 PM | |
| 1 | 08-09-2025 04:02 PM | |
| 1 | 08-10-2025 06:43 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|