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.
85 results found
-
Allow the capability to deploy to multiple Salesforce organizations within one deployment
Currently you can only push to 1 Salesforce org, however, we manage multiple organizations and would like the capability to push the same package to multiple organizations
2 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.6 votes -
Allow masking of State and Country to recognize API values
If the State and Country lists have been updated so the API values are set to ISO country codes the Masking of those fields during a data deployment does not work.
Data Load errors: '"FIELDINTEGRITYEXCEPTION:There's a problem with this country, even though it may appear correct. Please select a country/territory from the list of valid countries.: Billing Country:BillingCountry --"'Disabling masking works around the issue.
It would be great if the application could check the State/Country list and utilize the API values for masking.1 vote -
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 -
Show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB
I suggest you have functionality to show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB
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 -
Include validation rules and triggers of managed packages in 'Compare and deploy disabled rules'
When configuring a data deployment there is an option to disable validation rules and triggers on the target org. However the validation rules of objects of a managed package don't get included in this comparison. Triggers of a managed package are also not included.
I'm not sure if it will be possible to disable the triggers, but for validation rules this should be possible.
3 votes -
Preview of records for data deployment
It would be great either via the UI or a downloadable file/CSV, if we could see all the records that will be migrated in the data deployment. We're able to see the list of successful or failed records after the fact, it'd be nice to see the list of proposed records before hand. This would help identify if we're in the correct ballpark, say 500 records vs. 5000, and not knowing that until after the deployment gets attempted.
4 votes -
Deactivate email deliverability on Data Deployment
User email are masked in Sandboxes and we can mask Contact emails as part of the data deployment. This still leaves the Org Wide addresses as valid emails. If there is automation that is generating emails related to the data that is loaded, they will be delivered to the Org Wide Addresses.
It would be useful if the same script that is deactivating validation rules could set email deliverability to systems emails at the same time.
In the even that email deliverability was set to all emails in the Sandbox and not adjusted before the data deployment we would have…
5 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
5 votes -
Allow 'OR' combination for multiple External ID's in Upsert operation
Gearset allows the selection of multiple External ID's in an Upsert operation as part of a Data Deployment.
However, the system implements an 'AND' combination across all the external ID's specified on the object.
Effectively, ALL external ID's need to be present on the target side for the match to be identified and record upserted. If all external ID's are not present, the system performs an Insert on the target org.Please allow an 'OR' combination across multiple External ID's. Arguably, this should be the default option, but at the very least, a user needs the ability to decide how…
4 votes -
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 -
Add the concept of Master seeding object
One great feature to have, would be the possibility to identify a Master object from which the filters applied on it would be applied on all dependent objects automatically.
2 votes -
Use external script/template for masking data
I would love to be able to use my own script/template when doing just data (not having the compliance option) to select what fields I want to mask and the format for how I want to mask them. I will explain more.
When doing a data deployment (data seeding) to our developer sandboxes, I would like to be able to use an external script/template for masking data. In my script/template would like to be able to set the format for the masking and how much of the value to mask. For instance maybe I want to mask a phone number…
2 votes -
Allow for cross-object mapping with the data deployment add-on
It would be so powerful to allow users to map data to different objects using the data deployment tool. It would allow us to move data efficiently between orgs that don't have completely aligned object APIs and metadata.
3 votes -
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
2 votes -
Added an 'Or' function to the Filter Options
Right now there is only an 'And' filter when configuring Fields on the same object. It would make this much more powerful of a tool if we were able to chose between 'And' & 'Or'.
5 votes -
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 -
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.
2 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
1 vote
- Don't see your idea?