I think I’ve made this suggestion elsewhere but I couldn’t find a post, so I’m writing it up here just in case.

The idea: Please add a toggle to the scheduling config in Data Designer jobs for “Cumulative”. This toggle would cause the Data Designer job to append new records to the existing dataset on every run, vs overwriting the entire table with fresh data.

As Data Designer continues to take a more prominent role in Gainsight, it has basically replaced using rules to load to a custom MDA when admins require a complex dataset. This is well and good - it’s basically the same, but the Data Designer job creates an MDA and schema for us. Awesome!

There’s one major catch: DD can’t handle timeseries data collection, because it overwrites the old dataset on each run. This makes it unsuitable for “snapshot” style datasets, among other things - we’d have to fall back to the older method of routing data to a custom MDA via a rule for that.

In order to elevate the utility of Data Designer to the next level, a toggle allowing us to choose whether each DD job behaves iteratively (overwrites the entire dataset with fresh data each time) or cumulatively (appends new records and keeps the old data) would eliminate the functionality gap that brings us back to the older method via rules.

This absolutely does need to be a TOGGLE, specific to each DD job, and controllable by the admin - some use-cases for DD (JO sources especially) are still best served by the iterative behavior.