The ELT DML snaps (namely the LOAD, INSERT-SELECT, MERGE INTO, SCD2, EXECUTE) were intentionally designed to not execute in Validation mode (Design mode) for the following reasons:
In order to understand your problem better, can you provide some example use cases? This will help us in addressing the problem.
I understand your 2nd point and that is something a customer’s development team should be considering anyway to ensure the usage costs are managed.
As for your first point other than the obvious push down behavior why would these snaps behave different than to other DML snaps in other snap packs? Isn’t “Design Mode” just doing a limited run of the pipeline snaps? The only way to validate your pipeline is to run it and if there are any exceptions you need to be an admin in the environment to see what Snaplogic has sent to the DB. We have already discussed this with your product team and they told us this was a large level of effort and needed more customers to request this behavior to put it into roadmap, they never mentioned the corruption issue. We would never validate or go into design mode in a production environment any.
