It is mostly impossible. Compilation errors (when you save enabled directive in maintenance UI) come from C# compiler.
In general, directive validation should cover your needs. But it should be improved definitely.
They only look similar. But they are completely different sub-systems. Anyway, the new UI will use way different approach.
I thought about this approach. The main “blocker” is targeting. Existing import/export UIs cover both MD and DD. Putting them into the action menu conflicts with this behavior.
Also, I’d prefer to completely remove Import/Export from BPM in favor of the new solution workbench (if and when it will be ready).
In general, it is possible already (if you have a group and select overwrite mode).
However, I understand what you mean.
There are two problems here:
- Since BPM does not support company mapping (how it is implemented for EFx), copying is the only way to use same directive in a few companies. And it makes overwriting much more complex. Especially since directive name is not an id and can be changed in one of the companies.
- I have a few ideas how to improve that, but no ideas how to migrate existing environments.