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.
53 results found
-
Stop the reordering of XML when deploying to git
At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.
32 votes -
Add RecordType support for PersonAccount
Problem analyzer is always trying to remove my picklist values from any RecordTypes on PersonAccount. I am forced to use a custom "Problem analyzer template" where "Remove picklists from record type" is disabled.
Suppose I have a field called pickme: Account.Pickme--pc | Contact.Pickme--c it shows up in the record type XML as Pickme--c, and it seems like gearset tries to find a picklist on account with that exact API name, which will of course fail. My ask is that rather than raising an error at this point, GS should repeat this check on the contact object where it would find…
16 votes -
"Changed on" date on source control side of comparison does not show
We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.
10 votesThat is something we should definitely show. We’ve added it to our investigation list to see if it can be added into the app.
Thanks,
Jason. -
When Field is Deleted Permission Set changes are not recognized for the Field
Let's say we have only one object in the system. Addressc. And we have one Permission Set -> "System Administrator" with only "FieldPermissions" for all fields in the "Addressc" object.
Now I wish to Remove 2 Fields from "FieldPermissions" of the "System Administrator" Permission Set.
1st Field I'm removing just because I do not want the permission to be in the Permission set
2d Field I'm Removing from Permission Set, as I have physically deleted the Field.On Compare And Deploy Page I will See Deleted Field and I will see only one Section to be removed from…
9 votes -
Keep list of specified tests
When choosing specified tests to do a validation, let's say from a comparison that was created from a bunch of drafts that were combined, the pop-up will show the specified tests that were chosen originally for those drafts that were combined. That is awesome and is exactly what I want.
The problem is the "Fetching test classes from Salesforce" then occurs automatically and replaces that list with the full list of test classes, and check the boxes for all of them, replacing my existing list. That means I have to go back and choose my list of specified tests again.
8 votes -
Don't change the first 2 rows of a metadata file in version control
Usually a Metadata file retrieved from Salesforce starts like this:
<?xml version="1.0" encoding="UTF-8"?>
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">So two lines, first with the version and encoding UTF-8 and second with the type of metadata.
Now when GearSet does the deployment to version control, either from an Org or a Branch it uses this styling of the first row:
<?xml version="1.0" encoding="utf-8"?><PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
So everything on one line, with the encoding in lower case.
I don't see a logical reason this should be different in the files and is then causing differences in the version control system.
Thanks for looking into this.6 votes -
Scratch orgs with packages with InstallationKeys fails to install in CI
When creating a new scratch org you have the option of specifying the package and the installation key. This option is not available in a CI job to scratch org target scenario.
When there are dependencies specified in the sfdx-project.json file that requires an installation key the CI job run fails when the CI tries to install them.
There needs to be a way to specify the installation key, either by a custom JSON field in the sfdx-project.json, or on the CI job itself.
5 votes -
For Deleted components, "Changed On" date should be date component was Deleted
After doing a major changes in an org, one can be left with a lot of deleted components to deploy. In the comparison view, they don't show up as expected. The Changed On" date isn't the date deleted. It uses the last modified date in the destination. So deleted something last week could up as last modified 2 years ago.
Ideal: Gearset would to get the Setup Audit Trail via API and display the actual deleted date of deleted components5 votes -
Search on comparison doesn't search though object child items
When searching on the comparison results screen the child items of an object are not part the search unless you expand the object.
If you expand and then collapse the object tree child items do then appear in the filter search. It appears to be just on initial loading that it doesn't work.
4 votes -
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 -
When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist
When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.
4 votes -
Include a field's permission if the field is flagged as a missing dependent component
If a field is identified as missing from the deployment and the user agrees to include it, the corresponding field's permission should also be added.
4 votes -
3 votes
-
Optimize comparison list view
The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.
There is a common pattern for handling long lists like this, in…
3 votes -
Deployment of pre-valided package doesn't include accurate test counts
We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.
Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?
3 votes -
False positives in managed code
When I enable comparing managed packages (e.g. when I have added a field to a managed custom object), I get lots of false positives saying that there are differences in apex code.
On the source org, the code is show as "(hidden)"; on the target it is shown as empty. And Gearset lists this as a change.
Obviously, I know it's not a change, but it adds a lot of clutter to the comparison view.
3 votes -
Gearset Unit Test Monitoring ignores test methods in classes at V27 or earlier
For older orgs, one may have Apex classes at V27 or earlier. Such classes were allowed to also include testmethods.
Gearset's Monitoring job ignores these test methods leading to a false sense of security that one's org is "correct"
Example class is at V24
class Foo {
void doStuff() {}
static void testmethod myTest() {
new Foo().doStuff();
System.assert(...);
}The myTest will not be run by Gearset Unit Test Monitoring. It will be run by Setup > Apex Test Execution > Foo > Run tests
2 votes -
Update Deployment Functionality for Education Cloud Standard Picklist
Currently, Education Cloud standard picklist field values are able to be deployed to production. However, the deployment lacks the ability to define active or inactive picklist values. The workaround is to manually activate and deactivate these values after deployment.
This functionality was recently changed on 8/17/2023 for the Academic Session Season and Academic Session Type fields. Requesting the change to be made for all of these fields. Salesforce Education Cloud developer docs (https://developer.salesforce.com/docs/atlas.en-us.edu_cloud_dev_guide.meta/edu_cloud_dev_guide/edu_cloud_intro.htm)
2 votes -
Recognize code formatting changes as differences that can be deployed
If an Apex Class or other code file has been modified to fix formatting only, changing the indentation size for example, Gearset doesn't recognize this as a change that can be deployed. Formatting changes are recognized by git and SFs own source tracking feature so it should be recognized by Gearset.
2 votes -
gearset doesn't seem to pickup date of change for custom field and custom metadata.
gearset doesn't seem to pickup date of change for custom field and custom metadata.
2 votes
- Don't see your idea?