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.
71 results found
-
Select the fields to deploy during a data deployment
Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.
18 votes -
Compare and Deploy Attachments and Files
Please add the ability to use the "Compare and Deploy" for Attachments and Files. The ability to migrate PDFs, image files, word docs, and excel spreadsheets would be GREATLY appreciated! Thanks!
18 votes -
Delete records from the target org during a data deployment
Provide options to delete records from Target Org. This will help clean up of test data and reload from Source.
15 votes -
Allow components to be added or removed from an data deployment template
Currently when a data deployment template is created, there is no way to edit the template after it is saved so that components can be added or removed. It would be helpful if we could modify the components in the template without having to create the template from scratch again.
14 votes -
Enable Field Level Mapping for Data Deployments
Currently there is no field mapping option available for Data Deployment of Objects. This is a big blocker if we want to migrate selective fields data across Salesforce instances.
13 votes -
Schedule data deployments
The current data deployment functionality works fine for one-off deployments, but if you are trying to keep specific data in sync across multiple orgs, the ability to schedule data deployments for a given time in the future would let you deploy on a recurring basis automatically. Becomes especially helpful when combined with the current data filtering options.
13 votes -
Add Support for Pre/Post Data Deployment Scripts
Some of my more complex data objects require that I turn off Validation Rules during deployment, then back on again after deployment.
Options that would work:
BEST: List of Validation rules under each object and and option to temporarily disable on a one-by-one basis during the deployment. A "Disable All Validation Rules During Deployment" option would be helpful if this feature is implemented.
BETTER: Ability to specify metadata xml to apply to each sobject pre and post deployment.
GOOD: Ability to specify anonymous Apex to execute pre and post deployment. This would involve a callout to the Metadata API, which…
12 votes -
Set fields to a specific value during a data deployment
When deploying Data, it would be nice to be able to set field values. It could be just to null them or set a value. It could be part of the configuration or data masking.
11 votes -
Select a set of data deployment templates and run them in order
Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.
9 votes -
Support user record migration from production to sandbox or scratch orgs
New users are often created in the production org that need to be monitored and brought back to sandboxes as well. It would be great if the data deployment tool could support moving user records from prod to sandboxes or scratch orgs.
9 votes -
Allow complex filters and child relationships on filters for data loading
Allow complex filters and child relationships on filters for data loading. For example, filter the Account to only load if the Owner is an Active user in the system.
9 votes -
extend the GearSet public API to include Data deployments between Sandboxes and Scratch Orgs
Allow triggering Data deployments via the public API to eliminate having to sync data manually. This also includes triggering creation of Scratch Orgs via the Gearset API so that Gearset can instantly recognize them them.
The workflow we would like to automate is: feature branch is checked out which triggers a CI/CD system pipeline to create a corresponding scratch org, do a metadata deployment from a test sandbox, and sync data from the same test sandbox. This allows us to create on-demand full copies of the environment for purposes of E2E testing (inc. external integrations) and feature development that requires…
6 votes -
Allow record data load from CSV file
While it is nice to deploy record data from org to org with Gearset, it would also be nice to be able to deploy data from a CSV file, with the ability to custom map the headers. Native Salesforce Dataloader has this capability, as well as many 3rd party tools out there. Please incorporate this capability into Gearset.
6 votes -
Allow Data Deployment to filter lookup fields on fetched data
Currently, when doing a data deployment Gearset will let you know of all the referenced objects from the object you selected. What it doesn't do is the opposite of that - let you know all the objects that reference your object with a lookup.
It'd be great if we could add a filter to utilize some data pulled in a fetch/query during data deployment.
ex. field (TeamMember.ProjectLookup_c in {returned Project results in query in previous step of data deployment).
6 votes -
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
4 votes -
Select all objects in a data deployment
It would be useful to select all objects in the data deploy screen to make it faster to select a large number of objects (even better would be the ability to group objects and select whole groups at once)
4 votes -
I would like to be able to deploy directly from environment variables.
This feature would allow me to setup each sandbox environment after doing a refresh from production.
3 votes -
Create a Data Deployment Template for migrating Territory Management (1.0 & 2.0)
I would like to see a gearset defined template for Territory Management in Salesforce. I am definitely in need of this functionality as it seems to be a post deployment step once you deployed all Territory Management metadata.
in ETM 2.0 for example, after deploying the related metadata you need to deploy all related records for UserTerritory2Association Object, this contains who are the users assigned to a territory.
Not a big template but can be a good thing to have as a preset.
3 votes -
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.3 votes -
Retain Deployment Friendly Name and Notes After Failed Deployment
When attempting to validate a deployment, and the validation fails, Gearset retains the deployment's friendly name and notes fields from the validation. The user can make any necessary changes to the deployment, and won't have to re-type this information when attempting it a second or third time.
I'd like to see this same functionality when dealing with a failed deployment that doesn't use validation. Validating a package takes two steps (long steps), and typically I only want to use this option when delaying a deployment. However I often use it anyway just so I can retain my data in these…
3 votes
- Don't see your idea?