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.
75 results found
-
add a column for file sizes and show a warning message if over the limit (might happen deploying content assets)
Recently when deploying a large amount of content assets, I ran into a issue where the deployment would freeze on caching metadata for faster comparison.
Support told me the deployment size was too large and I broke it up into smaller deployments. I suggest adding a column with file sizes and perhaps a warning message if you exceed the deployment limits.
4 votes -
Create a link in the main menu under Data Deployments for managing Data Deployment Templates. It is not very intuitive to manage them curren
Create a link in the main menu under Data Deployments for managing Data Deployment Templates. Having to start a deployment in order to manage the templates is not very intuitive.
1 vote -
Add navigation options to the data deployment process
We are making use of the data deployment tool to seed our sandboxes with test data. When you execute a template it always navigates you to the last step (which makes sense). There are times however that we need to go back to the 2nd step and change filter criteria. This includes several clicks and waiting for pages to load.
Is it possible to add a navigation bar at the top that shows the various steps so you can quickly jump to one you need to update?
ie Step 1 > Step 2 > Step 3 > etc1 vote -
Make filter to search through all the components which are hidden under 1st level and expand the components
Can I ask Gearset team to add filter in compared components to search through all the components which are hidden under 1st level (e.g. custom objects or profiles).
For example, in the filter to compare metadata I selected certain custom tab (in the profile the access to the tab was deleted), also selected certain profiles, but serching through the compared metadata list I spent hours and did not manage to find those components for deployment package.
The same is for object access. I selected certain object, selected certain profiles - and again, it's a hard quest to find necessary components…3 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.
15 votes -
Implement Data migration support for nCino
nCino is a native Salesforce application for banking customers, configured using records, similar to how CPQ is configured. Deploying the data based configuration from environment to environment can be very difficult and painful. This would be a valuable feature for every nCino customer
3 votes -
1 vote
-
When cloning a deployment, also clone the test settings
When I'm cloning a deployment, if in the original one I have selected specific test classes, by default have those selected again in the clone.
Often you either need to repeat a deployment, or you'll deploy several times between instances, with the same tests.
1 vote -
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…
8 votes -
Provide More Detailed Information on Data Deployment Summary Steps
Currently the data deployment summary displays an elaborate interface but with very little useful information other than record counts. On the right side are Steps, but those steps do not tell the user much. I can see that in one step x records were fetched, for example, and in another step y records were fetched, but I can't see WHY.
Example use case: I had a situation where I was filtering an object but the filter wasn't being honored (more records were being deployed than expected). I could see from the data deployment summary that one of the steps was…
1 vote -
Add a way so we can easily integrate commits into Salesforce.
What I mean by this is, give users the ability to create and associate commits from in Gearset to a custom Object in Salesforce.
The commit would create a new record in Salesforce, under the custom object, let's call it 'Commits'.
We'd be able to pass through data such as the commit status, the ID of the commit, a link to the commit itself taking us back to Gearset, the name, and author, etc, etc...
I'd imagine this is possible through the use of the BitBucket API, however with SF teams who lack developer resources, this would be a nice…
1 vote -
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 -
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.
4 votes -
Data Deployment Template that supports complex rules
Looking to be able to setup a Data Deployment template that supports complex rules with record limits.
For example...
- Select 100 accounts that have been modified recently that belong to division A that contain at least 1 contact, 1 opportunity and 1 activity.
- Select 100 accounts that have been modified recently that belong to division B that contain at least 1 contact, 1 opportunity and 1 activity.
- Select 100 accounts that have been modified recently that belong to division C that contain at least 1 contact, 1 opportunity and 1 activity.Currently have to build 3 or…
2 votes -
Allow Data Deployment to handle more complex structures
Currently, user is able to select Obj A, Obj B that references Obj A, Obj C that references Obj B. And, in the next step of data deployment it allows user to select Objects where Obj A, B or C, and objects references by those objects.
If we ignore above example, I want to be able to select: objA(id), objB(id, objA), objC(id, objB, objD), objD(Id), objE(Id, objD). Where the first object I select and everything else is filtered on is objA.
1 vote -
Provide a better error when "invalid or null picklist values" is thrown.
"invalid or null picklist values" is thrown and i have too many picklists to figure out which one is the issue. Please provide speicific fields that are causing errors.
1 vote -
whenDeploying metadata and linking it JIRA Issue it will be good idea to have more Jira Issue fields visible not just Jira Issue key(id).l
when Deploying metadata and linking it JIRA Issue it will be a good idea to have more Jira Issue fields visible not just the Jira Issue key(id).l would like to have Issue "Summary" field Visible
2 votes -
Data deployments should ask if you want to Insert or Update or Insert & Update data
Data deployments should ask if you want to Insert or Update or Insert & Update data.
Currently it always performs data upsert only
1 vote -
One-click Sandbox data deployment of all objects
I think a great feature would be for the tool to be able to copy all object data from one org to a sandbox, and if the amount of data is too large for the sandbox, allow the user to specify what objects to take sample data from - and how - i.e. take no data from a certain object,or take 5% of the latest created data, etc. It would be helpful to show the objects that have the most data.
1 vote -
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
- Don't see your idea?