Has anyone encountered issues with the --force-cascade-delete option during configuration deployment?
Over the past few years, we’ve faced recurring problems when deleting Properties in our Person and PersonRecord EntityTypes. We make a conscious effort to reuse TargetColumnIndices (TCIs) whenever possible.
We’ve observed two specific issues:
-
Although the TCI appears to be available in our configuration, the deployment fails with a “duplicated TCI” error.
-
When reusing a recycled TCI (often for boolean properties), the newly created property — which should not have been initialized after deployment — appears as already checked in our workflows.
Has anyone experienced similar behavior?
If so, were you able to identify the root cause or implement a workaround?
Any insights would be greatly appreciated.