|
POST
|
@BrianKreb please update to the ArcGIS Pro 3.0.4 patch which has been available for a few weeks to see the issue resolved. https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDE1Mjc4Ng==
... View more
02-28-2023
11:17 AM
|
0
|
0
|
7205
|
|
POST
|
This might be a known issue already logged to Esri Support, BUG-000154896. "In ArcGIS Pro 3.0.3, right-clicking a layer created in ArcGIS Pro 2.8 in the Contents pane to export features does not include all of the fields in the attribute table." I can determine if it's the same problem, by looking at the layer file, which you can generate by right-clicking the layer, select Sharing>Save As Layer File and email the result to dflater@esri.com. The layer file doesn't contain any sensitive data, only the layer property definitions. You can also try searching for "Copy Rows" in the geoprocessing pane and use that simplified tool to export the output .csv. The problem above relates to the Field Map parameter of the export tools.
... View more
02-27-2023
05:23 PM
|
3
|
1
|
11292
|
|
POST
|
@VinceE I suggest to add a similar discussion to the ArcGIS Ideas site, where others can comment and this idea of enforcing contingent values in Calculate Field can continue to gather other user support. As a community question, this post has a lifespan and won't be tracked as a development request or priority. https://community.esri.com/t5/community-help-documents/arcgis-ideas-submission-guidelines-and-statuses/ta-p/904874
... View more
02-07-2023
05:26 PM
|
0
|
0
|
3117
|
|
POST
|
I've confirmed what @ChrisRingo describes above. When using a value table with feature layer and field pairs, the field column automatically receives a dependency on the feature layer column. When using a value table with raster layer and field pairs, this dependency is not achieved and does not appear like it can be forced. This is a defect that we will correct in a future release. There is not a workaround possible that I'm aware of at this time.
... View more
02-02-2023
11:28 AM
|
1
|
1
|
2013
|
|
POST
|
@CeciliaMartinelli and all, just to let you know, the issue has been resolved in ArcGIS Pro 3.1, which will be publicly available coming soon. And the fix is being backported to an ArcGIS Pro 3.0.x patch, which will probably be available around the same time (within a few weeks). For Tech Support tracking, it is issue BUG-000152786
... View more
01-18-2023
04:43 PM
|
2
|
0
|
2942
|
|
IDEA
|
01-03-2023
11:59 AM
|
0
|
0
|
4195
|
|
IDEA
|
The Append tool will do this in Pro 3.1 using addition Update parameters.
... View more
01-03-2023
10:18 AM
|
0
|
0
|
3443
|
|
IDEA
|
The workflow described can be accomplished starting in Pro 3.1, but not using the Calculate Field tool. The Append tool has a new geometry update mode and parameters to configure how the update should be made. This was covered in this newer Idea: https://community.esri.com/t5/arcgis-pro-ideas/gp-tool-to-batch-replace-geometries-from-one-fc-to/idi-p/1139522
... View more
01-03-2023
09:40 AM
|
0
|
0
|
2523
|
|
IDEA
|
An informational tip will be added below the Join Table parameter in a future release, to indicate that the specified layer/table has a definition query which will be moved to the input layer when performing the join. This is such a special case and behavior we agree the information should be presented directly to the user, not behind a small warning icon or solely in the tool documentation. An editable definition query control will not be placed on the tool dialog, that is outside what we can do at this time.
... View more
12-16-2022
11:26 AM
|
0
|
0
|
2897
|
|
IDEA
|
We can reproduce the issue with domain descriptions not being carried over to the output KML. This issue will be resolved in the near term. Note, we will make the Layer To KML tool honor the choice in the Transfer Domain Descriptions environment https://pro.arcgis.com/en/pro-app/latest/tool-reference/environment-settings/transfer-domain-descriptions.htm . So you will need to apply that setting to get the description values in the output KML.
... View more
12-14-2022
12:42 PM
|
0
|
0
|
3037
|
|
IDEA
|
12-07-2022
05:17 PM
|
0
|
0
|
2440
|
|
IDEA
|
This has been developed in ArcGIS Pro 3.1. Here is the new syntax that will copied to the clipboard when using the various Copy Python Command options. arcpy.management.CalculateField(
in_table="main.random",
field="testfield",
expression="200",
expression_type="PYTHON3",
code_block="",
enforce_domains="NO_ENFORCE_DOMAINS"
) As we feel this syntax matches best practices and standards for Python code, as well as having much improved readability, this is the default and only option when copying Python commands from geoprocessing tools.
... View more
11-22-2022
01:40 PM
|
0
|
0
|
4592
|
|
IDEA
|
This isn't something that would be provided as a core software geoprocessing tool in ArcGIS Pro. Based on the connections in the comments there might be other ways to achieve the desired goal.
... View more
11-18-2022
02:18 PM
|
0
|
0
|
1614
|
|
IDEA
|
11-04-2022
12:31 PM
|
0
|
0
|
3306
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 03-22-2024 09:27 AM | |
| 2 | 03-08-2024 01:56 PM | |
| 3 | 02-21-2024 11:58 AM | |
| 1 | 05-09-2023 02:24 PM | |
| 3 | 02-27-2023 05:23 PM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|