AdminGearset Team
(Feedback Manager, Gearset)
My feedback
60 results found
-
14 votes
An error occurred while saving the comment -
3 votes
An error occurred while saving the comment Can these users that you want to prevent still make changes in the orgs directly?
Our confusion rests on the problem that stopping them creating their own connections within Gearset, doesn't resolve your main problem of these users making changes in the orgs, or does it? -
2 votes
An error occurred while saving the comment This is explained in https://docs.gearset.com/en/articles/2292624-why-is-the-changed-on-date-sometimes-incorrect, can you see if we are missing something?
-
1 vote
An error occurred while saving the comment Just to clarify, is this referring to metadata deployment or data deployment?
-
0 votes
An error occurred while saving the comment Does the setting in https://app.gearset.com/account/notification-settings achieve this?
-
2 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment Are you referring to unlocked packages or is this something different?
-
1 vote
An error occurred while saving the comment Hi,
Do you have specific dropdowns in particular that you're referring to in the app?
We do have a lot which have filtering already with a similar mechanism although this isn't applied everywhere so any examples you have would be helpful.
Regards,
The Gearset Team
-
1 vote
An error occurred while saving the comment To help us understand the suggestion: how would this checkbox affect the results of the comparison?
-
6 votes
An error occurred while saving the comment As a workaround - would renaming the the job with a "zzz_" prefix move it to the bottom of the list - is that sufficient way to address your use case?
-
1 vote
An error occurred while saving the comment Is the suggestion to allow downloading of the metadata xml as a ZIP file (This is now available)? or is the suggestion asking for something different?
-
1 vote
An error occurred while saving the comment This is the PlatformEventChannelMember metadata type that needs to be added tot he Gearset metadata filter.
-
3 votes
An error occurred while saving the comment Hi Andre,
Thank you for your suggestion, can I ask what this export would give you or your clients that the Gearest comparison results page doesn't?
And what file format would you like this export to be in? Because a CSV file cannot capture the line differences in a meaningful way.
Regards, -
1 vote
An error occurred while saving the comment Is this the same issue as the one documented at https://docs.gearset.com/en/articles/2413367-why-is-xml-order-of-some-metadata-in-the-comparison-results-different or is there more/different nuance to LeadConvert?
-
3 votes
An error occurred while saving the comment Hi,
What sort of manipulations would you like to make in the CSV?
It'd also be great to hear what data masking options are missing at the moment.
Thanks,
Tom -
3 votes
An error occurred while saving the comment Thanks for this suggestion.
Can I ask for a bit of clarification? Are you asking for the number of XML line differences to be shown for each result or something else?
What would this number help you achieve?
-
2 votes
An error occurred while saving the comment For the record this is the middle bar referred to:
This is the info of the source and target, API version, status and package versions for Apex class. -
6 votes
An error occurred while saving the comment Additional background for consideration: note this is the case only when the "source control setting" [https://app.gearset.com/account/source-control-settings] > "XML quote escaping style" is set to
" for double quotes and ' for single quotes (Gearset default)
If the setting is set to
" for double quotes and ' for single quotes (Metadata API style)
The result is two lines as desired, first with the version and encoding UTF-8; however this is adding other changes to the way characters are escaped that causes the OP more problems.
-
17 votesAdminGearset Team
(Feedback Manager, Gearset)
shared this idea
·
-
14 votesAdminGearset Team
(Feedback Manager, Gearset)
shared this idea
·
-
1 vote
An error occurred while saving the comment Have you considered using Gearset's CI, configuring a job to export your production org to a git branch?
We have thought about this request and have responded in the documentation (https://docs.gearset.com/en/articles/5069914-delta-ci?location=conversation#h_c386626adc) as follows:
Delta CI jobs deploy everything in the source git branch that has changed since the most recent successful deployment from that branch.
The difference displayed in the run is between
- the new metadata items in the last commit on the source branch, and
- the previous commit on the source branch, when the most recent successful deployment occurred to the target organization
This is the problem with validation only CI jobs: as the validation CI job does not deploy metadata to the target, there is no previous commit which can be used as a substitute to the most recent successful deployment. As a result, we can't generate a delta CI job run in the same way as we can for deployment jobs.
We have considered several options, but we have not identified yet a suitable alternative to compare against. If you can think of any possible substitute. We'd love to hear from you.