|
POST
|
Is your join one-to-many? If the answer is no, are you 100% sure? I ask because one-to-many joins in ArcGIS Pro are pretty buggy. Is ArcGIS Pro the right tool for tabular/join-based geodatabase analysis? Possibly related: Export join to FGDB: Join table ID field is null Esri Case: 03616469 BUG-000146098 Join with definition query: Export has more rows than input (definition query is ignored) Esri Case: 03619440 BUG-000167563, BUG-000135505
... View more
07-30-2024
11:49 AM
|
0
|
11
|
5765
|
|
IDEA
|
@CM0001 Related: Symbology class unique values list — Select a symbol/row by clicking in the blank column
... View more
07-30-2024
07:55 AM
|
0
|
0
|
5866
|
|
IDEA
|
ArcGIS Pro 2.9.5; Oracle 18c 10.7.1. EGDB; line FC In the Symbology Pane > Primary symbology > Classes tab > list of symbols/unique values: I want to click a given symbol/row and delete it using the 'Delete' keyboard key. As mentioned in Remove specific symbol class from Unique Values list, we can click in the 'Value' or 'Label' columns to select a row. However, users often try to click in the blank column on the right-hand side to select a row; clicking in that column doesn't select the row. Could the blank column be enhanced so that it's clickable/selectable as well? I think that would be more intuitive. Otherwise, users get the impression that the rows aren't selectable at all since clicking the blank column has no effect. (Maybe users avoid clicking in the 'Value' or 'Label' columns because they think clicking will automatically go into text editing mode, which isn't what they want.) Edit: I suppose this idea applies to right-clicking as well. Right-clicking in the blank column has no effect, which is unintuitive.
... View more
07-30-2024
07:38 AM
|
6
|
1
|
1065
|
|
POST
|
Edited. Regarding this article: Why is the field set to blank instead of null and vice versa in ArcGIS Pro? A field can have a null value when the data type is set to numeric or the Allow NULL check box is enabled. It is not possible to have a blank value as an integer such as the number zero ('0') is also a value. For example, in an attribute table, when the value in the No. of Siblings field is deleted, the field is set to <Null> instead of blank, demonstrating the value does not exist. I'm finding the wording in that article to be awkward and misleading. For example, should the blue "or" actually be an "and"? I've submitted feedback via the feedback button. But I often don't hear back about feedback.
... View more
07-30-2024
07:10 AM
|
0
|
0
|
786
|
|
POST
|
How to Toggle Constraint and Calculation Attribute Rules on and off A somewhat related ArcGIS Online question: Is there a way to do a Bulk Attribute Update and avoid updating the LastEdited Editor Tracking Information?
... View more
07-26-2024
08:11 AM
|
0
|
0
|
2063
|
|
POST
|
I'm getting the "You don't have any notifications" error again.
... View more
07-25-2024
09:41 PM
|
0
|
8
|
2087
|
|
POST
|
It sounds like your data has a one-to-many relationship. Arcmap only supported one-to-one joins. But ArcGIS Pro supports one-to-many joins in some cases. In Pro, it will display duplicate rows in the attribute table for each of the workorders on the "many" side. But one-to-many joins only happen under specific circumstances. The short way of describing it is: if all your data is in the same geodatabase, then Pro will likely create a one-to-many join. But if some of your data is in Excel, then that means all of your data isn't in a single geodatabase, so the join won't be one-to-many, it will be one-to-one (one-to-first). You might find it hard to decipher the documentation when it comes to why Pro chooses to create a one-to-many vs one-to-one join: Add Join (Data Management). Hint: search that page in your browser for the word "many". This post might help make sense of why Pro made a one-to-many vs one-to-one join: Indicate what caused type of join to be used (1:1 vs 1:M) But regardless, Pro will tell you what kind of join it used in the layer properties: Just a heads up: One-to-many joins in ArcGIS Pro are quite buggy. You might find you need to export to a static copy (such as a separate feature class within the same geodatabase) in order to use the joined data in Pro. Is ArcGIS Pro the right tool for tabular/join-based geodatabase analysis? Disallow 1:M join layers as GP inputs instead of producing unexpected results
... View more
07-25-2024
12:36 PM
|
0
|
0
|
1393
|
|
POST
|
For what it's worth, your blurb where you say "I have a gdb that includes shapefiles" doesn't really make sense. Data is either in a geodatabase, or a shapefile, but not both. A geodatabase's layers are called feature classes, not shapefiles.
... View more
07-25-2024
12:25 PM
|
0
|
0
|
1394
|
|
POST
|
Related idea: Warning 003571 is not needed when using field calculator to set value to None
... View more
07-25-2024
12:15 PM
|
1
|
0
|
8573
|
|
IDEA
|
Related: Correlate open attribute tables with open map frame in Pro
... View more
07-25-2024
12:08 PM
|
0
|
0
|
795
|
|
POST
|
Related idea: Switch between saved/grouped attribute table arrangements It's almost as if I want to save attribute table arrangements to a given map. But I don't think that's how map views work in Pro projects.
... View more
07-25-2024
12:05 PM
|
0
|
0
|
1240
|
|
POST
|
Would it be worth submitting an ArcGIS Pro idea for this? At the very least, an idea would get Esri to confirm the functionality doesn't already exist in Pro.
... View more
07-25-2024
11:27 AM
|
1
|
1
|
3741
|
|
IDEA
|
For what it's worth, I noticed something about the "permanent symbology and labelling" bug in older versions of Pro that confuses users: If a FC has permanent labelling stored in the EGDB, including a labelling SQL definition (such as WHERE TYPE='B'), then that SQL definition gets applied to all subsequent labelling that the user might apply to the feature layer in the map. It’s confusing when that happens – not all features get labelled and the user doesn’t know why because they’re not aware that the labelling SQL definition exists. So that might be something to keep in mind regarding this idea.
... View more
07-24-2024
09:56 AM
|
0
|
0
|
4044
|
|
POST
|
Related: Documentation about new workspace caching functionality in Pro 3.3.0
... View more
07-24-2024
09:45 AM
|
0
|
0
|
2762
|
|
IDEA
|
ODBC can also be used to connect to enterprise geodatabases in MS Access and Excel. There might be a similar driver for connecting to mobile geodatabases, too.
... View more
07-24-2024
09:40 AM
|
0
|
0
|
616
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-20-2026 02:12 PM | |
| 1 | 03-19-2026 11:42 AM | |
| 1 | 06-03-2026 04:02 AM | |
| 1 | 03-18-2026 07:08 PM | |
| 2 | a month ago |