The Intersect 3D tool fails on multipatch feature classes containing GlobalID fields.

Workaround

Temporary Workaround

The only current workaround is to export the input feature class to a local version without the GlobalID field before running Intersect 3D.

This workaround is not practical in production workflows:

• It requires duplicating data or exporting selected features each time.
• It breaks the connection to the original dataset that relies on persistent GlobalIDs.
• In our workflow, 3D volumetric intersection between cadastral parcels is performed as part of a routine QA process for the 3D cadastre in Israel, where GlobalIDs are required and managed at the database level.

Why This Should Be Considered a Bug

1. No documentation indicates that Intersect 3D does not support feature classes containing GlobalID fields.
2. From a functional standpoint, there is no apparent reason that the presence of a GlobalID field should interfere with a purely geometric operation.
3. Intersect 3D is a commonly used tool worldwide, so it is surprising that this issue has not yet been reported or addressed.
4. The current behavior forces unnecessary data duplication and breaks standard data management workflows.

Request

• Confirm and classify this behavior as a BUG,
• Update the Intersect 3D tool to fully support GlobalID fields, or
• Provide clear documentation and meaningful error messages if this limitation is intentional.

This fix is important for supporting robust 3D cadastral workflows in production environments.

Steps to Reproduce