| Bug ID Number |
BUG-000180601 |
| Submitted | October 30, 2025 |
| Last Modified | December 18, 2025 |
| Applies to | ArcGIS Pro |
| Version found | 3.5.4 |
| Operating System | Windows Server |
| Operating System Version | 2019 64 Bit |
| Status | As Designed
After review by the development team, it has been determined that this behavior is as designed. See the Additional Information section for details.
|
Additional Information
When “all records” or “all rows” is specified during the replica creation process for a feature class or table, relationship class processing is not performed for that feature class or table during replica creation or synchronization, since all records or rows are requested. If the feature class or table is associated with a relationship class, post-processing of the records is performed to ensure there are no dangling relationships as a result of syncing all edits. If a dangling relationship is encountered, the foreign key is replaced with NULL.
Workaround
Use 'add with schema only' for Expand Feature Classes and tables.
Steps to Reproduce