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.
78 results found
-
Problem Analyzer should remove picklist values from record types when picklist values are removed from the picklist or value set.
When removing or deactivating a picklist value, Problem Analyzer should remove these values from any record types that reference them. While the initial deployment of the picklist may succeed, subsequent deployments of the referencing record types will fail if they still reference a deactivated picklist value.
1 vote -
add Dashboard owner to Problem Analysis to use user deploying instead in xml ref
Spring '24 Salesforce added ability to change Owner on a Dashboard https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_dashboards_change_owner.htm&release=248&type=5
"Previously, you had to clone or re-create the dashboard to provide access to a new owner."
This can now cause deployment errors when the Owner is changing between environments if the Uesr does not exist, similar to runningUser user references. Problem Analysis accounts for the latter, but not the Owner. Could we add the Owner scenario to this analysis rule?
1 vote -
apex classes dependencies
When deploying an apex class, check for dependencies. Currently it attempts to deploy even if there are missing fields and only reports missing fields one at a time. Very tedious to address.
1 vote -
Add to Problem Analysis option to auto remove DelegatedAccount tab settings
Add to Problem Analysis option to auto remove DelegatedAccount tab settings since it's an invalid tab and can cause validation/deployment errors. This saves a step of having to change Custom Object filter to Named Items and manually exclude DelegatedAccount when moving new profiles.
1 vote -
Highlight "Failed Validation" Components
If the metadata Deployment Validation step fails, and the user clicks the "Back to Comparison" button, the components that caused the failure should be highlighted on the screen for manual review.
Currently, when a deployment fails on the validation step, my process is:
- Wait until the Validation step is done
- Sort by the Status to show Failures on top
- Take a screenshot of the list of errors (hopefully less than a full screen of errors)
- Click the "Back to Comparison" button
- Use the screenshot like a checklist to work through the errors
- Run Validation…1 vote -
Enable data fixes when migrating Vlocity datapacks
When the data in the source and target environments are aligned, deploying Vlocity datapacks with Gearset can be quite straightforward.
However at times when they are not, deployments can fail catastrophically with the documented solution requiring the use of tools provided by Vlocity / Salesforce Industries in their Vlocity Build Tool : https://github.com/vlocityinc/vlocity_build. The alternative is to try manually resolving the issues, which can be an uphill struggle when you consider complexities around products, such as their hierarchy, availability and pricing.
For Gearset to truly be a one-stop tool for Salesforce Industries deployments, please enable data fix functionalities in…
1 vote -
False error - 'Field permission cannot be set for Required Fields'
Deploying few field permissions through CI, there is an error 'Field permission cannot be set for Required Fields' in the Problem Analyzer, but actually the fields are not marked as Required in the target. Lead.Pronoun, Lead.GenderIdentity fields.
1 vote -
1 vote
-
allow configuration of problem analysers for different target locations
If we could turn of problem analysers for specific locations (e.g. Git repos) this would allow us to remove irrelevant problem solutions from our git commits, but keep them for deployments
1 vote -
package missing -meta.xml endings
When I download a package from a CI Job, it doesn't include the require "-meta.xml" ending for my metadata types. I wrote the following script to add them back one folder at a time. It would make more sense if Gearset just gave me the correct filenames when I download the package though.
…# Gearset gives us a downloadable package to trouble shoot, # but it doesn't have the -meta.xml text appended to it. # Find all files with this ending and append -meta.xml to it. find ./ -type f -name '*.flow' | xargs -I '{}' mv '{}' '{}'-meta.xml find1 vote -
Option to download problem analyzer template
Option to download the problem analyzer template so users have an option to add it to the custom github actions scripts to run CI validations for their own delta comparisons.
1 vote -
1 vote
-
When Deploying A Page Layout, Consider Quick Actions to be Dependencies When Checking for Package Issues
Problem analysis doesn't catch if a page layout has a Quick Action that isn't present in the destination. This causes the package to error on send.
1 vote -
Don't include Wave dataflow deletes in package when Recipe is included
When deploying deletes of Wave recipes, if you include the Dataflow at the same time, Salesforce will fail validation with a DataFlow not found error. GearSet should be smart enough to build the package without the Dataflow if the corresponding Recipe is marked for delete.
1 vote -
Ability to see complete history related to a ticket or common name
It would be incredibly useful to have the ability to see a complete history related to a ticket or common name. For example, if I'm working on a Jira ticket named "SALES-123," I would like to be able to see all of the comparisons, branches, deployments, and promotions related to that ticket.
This ability would significantly improve the efficiency and effectiveness of troubleshooting issues.
1 vote -
Validation job when PRs are raised
Requirement :
Provide option to create a CI Validation Job only with "Validate pull requests targeting the source branch" and keep "Run Job" dropdown as optional .As Of Now :
When we raise a PR, it initiates feature branch validation ( cos, we enabled "Validate pull requests targeting the source branch" ), and after that when we merge feature-branch to target branch, it re-initiates another validation job.
For us, it's like similar validation is running twice on different events from which we can't opt out.Pros :
We can handle when to validate a feature branch, instead of bundling…
1 vote -
Warn if source version is greater than the version of the target org.
Often, salesforce will deploy the latest API version to sandbox orgs before production orgs. Therefore it's easy to use API version 55 in your sandbox and then get a failure message when you try to deploy it to your production org which is at version 54. Unfortunately, you have to start to validate your deploy before you get this message. This could be a pre-deployment issue that you can notified right away.
1 vote -
Provide help link/button on each analyzer problem pane with specifiec discussion
Suggestion
In "Problem Analysis" page, the problems indicated and solutions are not necessarily obvious and understandable.The suggestion to read more about the analysers in the user guide is in the case I'm facing an enormous challenge.
Copy and paste the problem into your search mechanism brings back endless answers - not one used the wording in the problem statement!.
Here's an idea, have a button/link with each problem that take one to the user guide section (or other documentation) exploring the problem.
No hunting for answers as the 1st choice to figure out what your product is saying. It's…
1 vote -
Apply certain PA outputs back to the comparison as a "quick fix"
The main example where I have wished for this pretty strongly is the "missing permissions" PA. This is the one that warns "not all permissions are included in the deployment". It would be useful to be able to go from that PA to a view where one could either add all the missing permissions in one go, or do so selectively by profile or permission set. Right now one has to screen scrape the output, paste it into a text file, go back into the comparison and laboriously hunt through the comparison to find the missing nodes, then add them.
1 vote -
Provide output from Gearset during the validation in terms of what tests were being run
I had unit testing jobs running ALL tests in source (full sandbox) and target (production) org - resulting in 80% and 79% test coverage. However, when I started to deploy my changes - the validation failed because test coverage was only 74%. Finally, after a few days, I figured it out.
I was just simply clicking "Validate" (i.e., did not choose specific tests). In the past - that ran "all tests". But something seems to have changed. When I picked "choose tests", about half the tests in my org were "automatically selected". I manually selected all other tests - effectively…
1 vote
- Don't see your idea?