Pankaj
My feedback
-
9 votes
An error occurred while saving the comment Pankaj supported this idea ·
-
11 votes
An error occurred while saving the comment Pankaj commented
I came across this need when doing data deployment configuration specifically for CPQ objects, where we have can only upload in-active consumption schedules as the Consumption rates is child object and deployed later and CPQ validates that Consumption schedules cannot be active without related Rates. Here I thought while data migration if I could select the IsActive fields value to false, that would save me 2 manual operations.
I expected that to be possible using Data Masking, but unfortunately we cannot specify values in Data masking.
Again quite useful feature for a proper ETL tool.
Pankaj supported this idea ·
-
14 votes
An error occurred while saving the comment Pankaj commented
This is a very important feature in any ETL tool. Exclusion of certain fields is a must feature for data migration for various use cases.
Also I totally agree with David Spell's comments for that feature to be "Deploy everything except these fields" as that will save number of clicks for users. Exclusion of fields are less and by default all fields should be selected on the UI presented to exclude certain fields.Pankaj supported this idea ·
this is definitely needed for periodic CPQ data deployments which needs to be run in sequence of dependent objects put into different configuration templates.
Also this can be useful for many other use cases that cater to Sync data from one org to another org.