Maybe a silly suggestion but would it be possible to have a sandbox option to run, for example, an insert action but only sandbox it so the results are not actually inserted, to test complex actions prior to bulk inserting a load of test data repeatedly in to a live environment? We currently implement a dumping-ground table for this, duplicate said table and rename it accordingly (often filled with utter garbage but no harm done and an easy clean up)… That way when we are happy we truncate this table and switch the insert to the ‘production’ table. To be able to sandbox these actions for debugging would be great!
Hope that makes some sort of sense?
Community Page
Last updated:
Last updated: