ArcGIS Pro Foundation common mistakes
ArcGIS Pro Foundation · Understand the traps and how to avoid them.
Assuming a newly added layer's coordinate system defines the map's coordinate system, then reporting data in the wrong CRS.
Candidates confuse the map frame's coordinate system with each layer's source spatial reference; Pro projects layers on the fly, so layers with different CRSs display together and the mismatch is invisible.
What to do instead
Inspect the map properties to read the map's coordinate system separately from each layer's source CRS; remember on-the-fly projection affects display, not the stored data, and only the Project tool rewrites a dataset's CRS.
Deleting a feature class or raster from the Catalog pane expecting it to be recoverable from the project, then finding no copy exists.
Candidates treat the Catalog pane as a document workspace like a map, forgetting that Catalog operations act on files on disk or in a geodatabase, not on project-only references.
What to do instead
Verify whether an item is a stored dataset or a project reference before deleting; use project backups or copies for safety, and remove layers from a map (not datasets from disk) when only the display should change.
Editing a file geodatabase feature class inside a map while another process or lock holds it, then hitting save failures or lost edits.
Candidates do not check for locks, open attribute tables, or concurrent sessions, and Pro blocks schema and edit operations when a lock exists.
What to do instead
Close open tables and other sessions, check for lock files, and stop edits before schema changes; save edits incrementally rather than batching a long session.
Building a layout at the wrong scale or extent, so the exported map does not match what was reviewed on screen.
Candidates set extent and scale on the map view rather than the layout's map frame, and each map frame carries its own extent and scale settings.
What to do instead
Activate the layout's map frame and set its extent and scale there; verify with the layout's scale and extent controls before exporting.
Applying symbology or labeling changes to the wrong layer or to a copy, then wondering why the map did not update.
Candidates edit a layer in one map while viewing another, or change a layer file without applying it, because Pro allows many maps and layers referencing the same data.
What to do instead
Confirm the active map and selected layer before editing symbology; apply saved layer files deliberately and check the Contents pane for which map and layer received the change.
Treating a definition query as a permanent data filter and expecting the excluded records to be gone from the dataset.
Candidates confuse display filters (definition queries, scale ranges) with data deletion, since both make features disappear from the map.
What to do instead
Use definition queries only to control display; use Select by Attributes plus Delete or the appropriate geoprocessing tool when records must actually be removed, and clear queries to confirm the data is intact.
Running a geoprocessing tool and assuming the output overwrites the input, then finding the original data unchanged or the output missing.
Candidates do not read whether a tool creates a new dataset or modifies in place, and do not check the output path and environment settings that control where results are written.
What to do instead
Read the tool's parameters to see whether input is modified; set an explicit output path and confirm the default geodatabase and overwrite settings in the environment before running.
Using a spatial join or overlay when an attribute join was intended (or vice versa), producing duplicated or mismatched records.
Candidates see both operations as 'joining' tables and do not distinguish matching by a key field from matching by location, so cardinality and geometry assumptions go unchecked.
What to do instead
Choose attribute join when a shared key field links records and a spatial join or overlay when location defines the relationship; check join cardinality and validate the result count against the input.
Sharing a map or layer package that references local paths, then finding the recipient's copy has broken data sources.
Candidates share a project or layer without consolidating data, so the package points to files only present on the author's machine.
What to do instead
Use the packaging or sharing tools that consolidate or extract data, verify the package contains the needed datasets, and confirm the recipient's environment before sharing.
Publishing a web layer or map with symbology or fields the target does not support, then seeing the published result differ from the project.
Candidates assume the project view equals the published view and do not check portal capabilities, supported renderers, or field visibility settings before publishing.
What to do instead
Review the sharing options and target portal's supported capabilities, simplify unsupported symbology, set field visibility deliberately, and inspect the published item after sharing.