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.
80 results found
-
Replicating Data should include backups as a source
Currently its possible to replicate data from a backup job by going into the backup run and clicking replicate data.
However, this is extra steps... its would be good if you could just select backups as a source from the data deployment screen.
1 vote -
Add ability to deploy ObjectTerritory2Association object
The ObjectTerritory2Association object does not get populated in the target org for accounts that are manually assigned to territories. This object is used by Territory Management 2.0 and holds the association between accounts and territories. After the deployment, I can see that this bridge object did get populated with the territory linkage for accounts that are automatically assigned to territories. This is expected because an insert of a new account with proper firmographic information will result in the account getting tagged to the correct territory (i.e. if the Account’s “Exclude From Territory” flag is not set to True).
However, there…1 vote -
Reuse earlier retrieved metadata, if nothing has changed
We have a large org and need to select many filters. A comparison take ages. Source of our deployments is mostly Git, which is very fast in retrieving metadata. I would like to have an option, to assume that nothing has changed in target and skip loading metadata of that org and use the metadata of an earlier comparison.
If we have a small bug in our Git (e.g, test class not correct), we get an error while deployment. That's okay. We fix it in about 1min and want to deploy again. Loading metadata from Git is instant finished loading…1 vote -
Force selection of fields to use instead of selecting id as default
In the select related objects page, Gearset selects id as the 'fields to use' field. If we are deploying a large set of data and by mistake do not change the 'fields to use' field then we end up creating duplicate records for Upserts. Would be great if there is an option to enable or disable the default selection.
1 vote -
Unable to import/export translations using .stf file using greaset
Currently gearset allows to deploy translations from one org to another org, however we do not have an option to do the translations using .stf file /excel for the fisrt time in any one of the org
1 vote -
Make Data Deployments Invocable (Salesforce APEX)
As a feature to enhance data deployments, make them invocable by Salesforce APEX (or other tooling) whenever a Sandbox is refreshed. Salesforce has a configuration to let the user specify an APEX trigger/class to run upon Sandbox creation. That could call the data deployments to run on the freshly minted sandbox, seeding it with data. This would enhance automation.
There are tools out there (like SFApex) that do something similar.
1 vote -
enable data deployment template merge
It is currently possible to select an existing template and add new objects and data deployment logic into it then save as a new template. It would save time to enable the selection of 2 existing templates and merge them into a single one.
1 vote -
Need to have JIRA integration with Data Deployments
Need to have JIRA integration with Data Deployments which will improve the process and allign it with meta data deployments
1 vote -
Ability to modify pieces of data before deployment of data
E.g when you want to move data from PROD to DEV there are some fields (e.g. Contract Status) that you want to move from Active to Draft. This should be a generic function also to be applied to other fields / objects.
1 vote -
Add a fast select check box to make sure you don't have to click each and every object
When you are in the data deployment setup you need to click each and every object. it's better to add a check box to include everything automatically based on a filter
1 vote -
Add a batch size option directly on Data Deployment and Data Templates
Currently we can specify the batch size for bulk data loads on Account level.
With this kind of setup we can't have two pararell jobs running on different batch sizes and we also need to memorize what batch size is required for each of my Data Templates.
It would be nice if we could do that directly on Data Deployment job and even save such setting in a Data Template.
1 vote -
Deploying to an org based on tags
It would be a useful feature to initiate a deployment when a Github tag is created.
1 vote -
Keep the same record owner between source and destination orgs.
Alternatively, allow the change of record owner before importing data to destination org.
1 vote -
Deploy Einstein Datasets from one org to the other
Copying of Salesforce objects with relations is a great feature. But this does not support Einstein datasets to be copied from one org to the other. It is critical for teams to have Einstein dataset in the lower orgs for development and testing
1 vote -
While configuring a data deployment, allow save after selecting objects and fields
There's no opportunity to save the data deployment settings after selecting objects and fields, and this can be quite time consuming, so if the job fails due to auth or other issues, right now, this requires the user to start over, and re-select objects and fields.
1 vote -
Allow deployment of Email header/footer changes
Examine changes to Email Footers and allow deployment of changes.
1 vote -
Support Salesforce standard Country/State Picklist Mapping for Data Masking
Right now, using the data masking feature for data deployments, the values for country and state are real values and random. There's no guarrantee that the country and state will be valid pairings.
This causes issues for orgs that use the standard Country/State picklists from Salesforce.
The goal would be that the masking feature would pull from the Saleforce default values and make sure that the state and country are valid pairings as opposed to randomizing both separately
1 voteGearset will now only use US states and “United States” for the country, meaning that the pairings are always valid.
-
Preserve auto-number field values during a data deployment
Staging environments typically exist with integrations with other systems that have references to auto-number fields
Data deployment re-evaluates auto-number fields instead of keeping the values of the source.If data deployment jobs could automate the following it would probably work
1. changing the type of the auto-number field to text in the target org
2. potentially removing apex references to the field
3. deploying the data
4. rolling back metadata modifications in steps 1 and 21 vote -
Add problem analyzers to the data deployment app
Much like the problem analyzers for metadata deployments in Gearset, it would be great if you could add a problem analysis feature for data deployments after having configured what you want to deploy.
Some scenarios will almost certainly cause the data deployment to either totally fail or only partially deploy some of the records and skip records it can't deploy. Providing automatic fixes (e.g. choosing not to include duplicates) would improve the number of deployments that work 100% of the time.
1 vote -
Allow serial deployment instead of parallel
When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.0 votes
- Don't see your idea?