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.
3 results found
-
Custom metadata retrieval failure
Looks like with the recent Winter 20 patch sandboxes deploys are failing if custom metadata is included in metadata filter. We had to remove the custom metadata from the filter to get CI jobs to run successfully.
The error was 'Salesforce reported an error (INVALID_TYPE: sObject type 'et4ae5MCOAuthClientDetailmdt' is not supported.)' which isn't even a metadata type in our org.
1 vote -
Monitor orgs - false positives in Clean Rules
It would appear that in the default 64 comparison set when using Monitor Changes, that SFDC may be returning fieldmappings in non-deterministic order when custom cleanrules are in effect as when Day n-1 org is compared against Day n org, the same cleanrule's fieldmappings are displaced some number of lines away causing a false positive. The obvious workaround is to remove Cleanrules from the metadata to compare but this means one can't detect true variances anymore.
1 vote -
Desktop Application does not save to history
Desktop Comparison and Deployment not visible in the web history.
Was using v1.0.2.2021. Compared Source: Local files, Destination: Sandbox.
1 vote
- Don't see your idea?