Help us improve Gearset
We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.
29 results found
-
Allow for the masking of data during a Data Deployment
During a data deployment it should be possible to mask the data in specific fields. For example, if I were importing Account and Contact data from production into a sandbox I would want to be able to mask email address so that we can't erroneously send actual customers emails while we're testing
4 votes -
Add "is empty" operator to data deployment filters
Add the empty operator or allow for '' or an equivalent to be considered a value for filtering while using the data loader, this would allow to use filters like where accountid='' or equivalent
1 voteYou can now use the is empty and is not empty filters on nillable fields.
-
Show source Org records count for each object so that we can decide on how much of it can be moved and how much of filter is needed
Show source Org records count for each object so that we can decide on how much of it can be moved and how much of filter is needed. Moreover after all object are select with filters for movement, please show the total number of records that will be migrated across all selection and its related objects. This will tell us if we are exceeding the limit of 10000 and do we need to split.
2 votesHi,
When you select objects for a data deployment, you’ll now see how many records the source contains for that object. This will also take into account any filters you have on the object.
We’d love to hear if this is useful or if there’s more you need – please get in touch via the in-app chat!
Tom
-
Ability to compare and migrate object data between Salesforce orgs
The metadata compare and deploy is outstanding and works well. What would save configuration and release engineers even more time would be an object data compare / sync. Sometimes, salesforce releases may only require a data migration. Hopefully, this feature will get a few upvotes from the community as well.
14 votesThis has now launched as part of our data deployment feature.
https://gearset.com/product/data-deploy
This is an opt-in feature, that doesn’t change the default security profile of Gearset for those users that choose to use metadata only
-
Preserve spacing in formulas!
When deploying components like workflow rules, workflow field updates, and validation rules, it would be great if the spacing (i.e. carriage returns) did not get lost after deployment. This is especially frustrating for complex formulas where care has been taken to properly indent the formula for easy maintenance.
6 votes -
Allow Migration of Data Records to Production
Salesforce CPQ uses Data for things that are traditionally done with meta-data. Due to this pricing logic, production configuration information, approval logic, and pretty much the entirety of the package is controlled with data.
Gearset has limited its data migration tool from being able to deploy data to a production org. This renders it useless when working with Salesforce CPQ and has me recommending competitors over Gearset to clients. Gearset is a better UI & workflow than other competitors, but this is a major flaw that should be removed!
3 votes -
View Data deployment history
Would be great to see the data-deployment history in Gearset UI. Also, the ability to replay them.
1 voteThe data deployment history page now enables you to view the deployment finished page for any of your previous data deployments.
With the ability to save a configuration template from a data deployment you can also then reapply the same configuration for the same source org in its current state.
-
Add the ability to filter by Date to Data Deployment
It would be very helpful to some processes I run if I could do data deployment filtered based on date - date created specifically. I am trying to migrate some test data from Production to QA/User Testing and I get duplicates now. A filter on created date would solve the problem entirely.
1 vote -
Ability to change the value of a field on import
Price Rules have Price Conditions and Price Actions and sometimes Lookup Queries hanging off of them as related objects. Some of the price rules wouldn't get created because there is a field called Conditions Met and it equaled Custom. If we were doing this migration via data loader, I would set those records to equal All for the value just to get the price rules in. Then we would load the Price Conditions. Then we would do an update to the price rules to set it to what it should be - Custom. We cannot save the record initially with…
1 voteYou can now deploy Price Rules and Price Conditions when Conditions Met is set to Custom. You’ll need to have either All or Any set as the default picklist value for the deployment to work.
It’s also possible to deploy Product Rules and Error Conditions, and Approval Rules and Approval Conditions.
- Don't see your idea?