What is a one sentence summary of your feature request?
Major bug : configuration deployment : Force Cascade Delete
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
We think there is a problem 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 2 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.
The --force-cascade-delete doesn’t purge the database of old values.
This regularly block our PRODUCTION deployments.
How do you currently solve the challenges you have by not having this feature?
We play around with TCIs until deployment succeeds. It is a major inconvenience.