Pro Migration lessons learned/issues

328
2
06-11-2025 10:50 AM
RyanKoschatzky
Frequent Contributor

Please post your experiences. 

0 Kudos
2 Replies
KevinKoester_KSDOT
Emerging Contributor

At the Kansas DOT, my biggest concern is mitigating version posting directly to default when we have external users that we can't stay in front of with regard to causing issues to larger batch processing inside of our GIS group...

AustinHimmelein
New Contributor

Creating a copy ALRS is not recommended by Esri, but we continue to use them. I could no longer pick and choose event layers to copy into a separate space to work with. With RH in Pro, you need to copy to entire RH DB to create a copy ALRS. This action has been transferred into a GIS data request and we request at least 2 copies a year for reporting purposes. 

Attribute Rules are the new thing with Pro. Arcade scripting is almost essential to unleash the full capability of attribute rules. When the Detect Overlaps for Linear Events tool was discontinued in 10.9, we had to rely on creating an attribute rule to perform this validation step. We are continually developing new rules but with a lack of Arcade expertise I feel our progress is slow. 

Don't expect to easily create PIPE CSV files with Pro, we had to discover a workaround after the arcmap tool was no longer available.