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.
1354 results found
-
Plain text list export of metadata
There are times when I'm in an email thread with other developers and I want to share a list of metadata that I'm trying to deploy via Gearset. It would be nice to have a button after a validation or deployment (failure or success) that copies in plain text a list of everything in the deployment. The list not only has the name of each metadata, but also the type of metadata it is.
1 vote -
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).
8 votes -
Improve error handling for invalid XML metadata files
Currently, when there is an error with an XML metadata file (usually introduced by git merges), Gearset will produce an error, either in the Initializing Comparison, or Checking Deployment stages, stating simply that "An unknown error occurred."
If Gearset instead ran the XML from source control through an XML validator using the Partner WSDL XMLSchema, then we could get file-level validation errors if the XML doesn't conform to what Salesforce's Metadata API will accept.
e.g.:
$ xmlstarlet val -e -s ~/Downloads/salesforce-schema.xml force-app/main/default/profiles/Marketing.profile-meta.xml
force-app/main/default/profiles/Marketing.profile-meta.xml:17108.15: Element '{http://soap.sforce.com/2006/04/metadata}field': This element is not expected.
force-app/main/default/profiles/Marketing.profile-meta.xml - invalid1 vote -
Reporting
have a way to dump a csv of the description of objects. i need to find a way to see what fields are encrypted.
1 vote -
Ability to see count of items per metadata type
Ability to see count of items per metadata type at the Comparison Result Page
1 vote -
Add the option to note successfully deployed components in CI notifications
When a CI job is configured to post to slack, and a job fails, it is very useful to see the message posted with information about what failed (error message, number of components that failed).
However, when a CI job succeeds, it only shows the counts of changed/new/deleted objects.
It would be very useful to have the option to list out what was deployed - this would make it easier for devs/qa users who monitor these slack notifications to understand which deployments are relevant to them at a glance.
2 votes -
Pulling object dependencies during data backup
A cool feature would be the ability for Data backup to have the ability to select object dependencies when you select a particular object for instances where you want to backup a subset of data and not just your entire org
2 votes -
Better error reporting when CI jobs fail.
Better error reporting when CI jobs fail. Many times I open a failed job and there are no errors reported.
7 votes -
Save deployment analysis suggestions and list of test classes
In order to make deployments more repeatable between orgs please allow a way to save the selection of deployment analysis suggestions an d list of test classes with a package. With a large package it can be difficult having to document or remember the same selections used in deployment to UAT org for Production deployment.
5 votes -
On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen.
On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen. We need a quick way to make sure that item level filtering is being used on each metadata type
1 vote -
The comparison screen takes too long to load and times out with large packages.
With large packages the comparison screen takes too long to load, >15 min, and can cause Chrome browser to time out. Can we have an option to not load the details of the differences in the bottom panel, only object names and then click a button to download only difference for a particular item on-demand? I normally don't need to see the diff
1 vote -
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.
14 votes -
track metadata filter changes
Filters are shared by default. However, if someone changes the filter, I cannot tell what has been changed, who made the change or when it was changed. Ideally, I'd like a version history for each filter.
6 votes -
Segregate metadata changes due to SFDC release
If I compare my production org to a preview sandbox that has been upgraded to the new release, I see some changed, new, and deleted items that appear to be due to the upgrade. For the most part it probably doesn't make sense (or isn't possible) to deploy those differences in either direction, so it would be nice to be able to exclude them or have them flagged somehow.
For example, in Winter '20 several fields were added to the OpportunityContactRole object. They show up as custom fields in the comparison. If I try to deploy them to production, the…
1 vote -
Permission sets not deploying correctly
When deploying a permission set, it was being deployed without the permissions checked, even though Gearset detects that the permission is checked in the metadata compare.
4 votes -
Show summary of selected Filter conditions
Would like ability to select a saved filter and see a summary of all the 'checked' filter conditions in it. Useful in verifying a filter or shared filter before using it.
1 vote -
Meta Data Searches
Ability to do a meta data search like you can in eclipse or visual studio in gearset.
For example search a custom field and where it is used within your org.
1 vote -
Explicitly set object-level permissions, even if these are omitted from XML provided by Salesforce API
Valerio recommended that I post this suggestion following a discussion on 29 August 2019.
Issue reference:
https://docs.gearset.com/en/articles/3226459-a-note-on-deploying-custom-object-permissions-on-new-profilesIssue:
1. Remove all object-level access for "Lead" from a custom profile in a source org
2. Deploy this profile to a target org
3. The profile in the target org will have access to the "Lead" object ENABLED, because this access is included in the Standard User profile (see document link above)The workaround (deploying and then deploying again) is cumbersome and not always practical, e.g. if making automated, one-step deployments outside of Gearset. Failing to make a second deployment means that…
25 votes -
Add an option to share orgs by default
Where we have a developer-manager, and a team of developers, it would be useful to be able to have a default for sharing org-connections where the manager always has access to their team's orgs.
At the moment, we have to share each org one-by-one.
This has caught us out where a dev team member validated a deployment, then went on holiday thinking that we could deploy it for them. They forgot to share the org-access, so we had to recreate the deployment to get it done.
2 votes -
Deploy data from local repository.
It would be very helpful if we could deploy data from a local repository. We have different namespaces for internal packages and it would make data migration significantly easier if we could do it from a local machine where we'd switch the namespaces.
3 votes
- Don't see your idea?