AdminGearset Team
(Feedback Manager, Gearset)
My feedback
61 results found
-
4 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Hi Brian,
Thanks for the feedback! We’ve looked into backup failures with GenAI metadata, and they seem to be down to missing permission sets.
If you haven’t already, check out this guide - it covers the permission sets you’ll need to get everything backing up smoothly: https://docs.gearset.com/en/articles/10406855-how-to-deploy-agentforce-genai-metadata-types
Let us know if that does the trick! Would be great to hear if it resolves things for you.
Thanks,
David -
14 votes
An error occurred while saving the comment With Flow Navigator, you can now choose which version of the Flow to deploy.
Learn more about Flow Navigator in this article: https://docs.gearset.com/en/articles/8989393-getting-started-with-flow-navigator
An error occurred while saving the comment If you are using v43 of the Salesforce metadata API to compare and deploy, this should be possible. If you are using v44+, the new Salesforce specification of the latest APIs removed support for that, so to achieve what is being asked here requires Salesforce's API to change before Gearset would be able to support this.
Is using v43 in the metadata filter an option for you? -
1 vote
An error occurred while saving the comment Hi Lee, have you got a link to the specific metadata that you are wanting?
The only metadata that I can find that seems related is here (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_cmsconnectsource.htm)
Which is CMSConnectSource.
Is that what you are wanting?
Just so we can begin to look into this for you.Thanks!
-
1 vote
An error occurred while saving the comment Hi David, I'm reaching out to you in the in-app chat to investigate this. Are you okay to respond there?
-
14 votesAdminGearset Team
(Feedback Manager, Gearset)
supported this idea
·
-
1 vote
An error occurred while saving the comment Hiya, does the release of the feature on https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/36282925-configure-which-problem-analyzer-results-to-use-in make this possible for you now?
-
15 votes
An error occurred while saving the comment What if the target is an org, or a metadata API repo?
Would you want the behavior to be only for SFDX source format repos?
The biggest question I have is "Would you be able to deploy that selection?" I understand that you cannot deploy a field on a object that does not exist. -
22 votes
All - please let us known in the comments which metadata types you would like us to support next with precision deployments. Thanks
-
1 vote
An error occurred while saving the comment What if the custom git repository connection is for BitBucket or Azure Devops? Would a "View on GitHub" button make sense?
-
22 votes
An error occurred while saving the comment This is now achievable with the release of the Automation API that Gearset has released. Please see the documentation on https://docs.gearset.com/en/articles/6341493-getting-started-with-the-gearset-automation-api
-
25 votes
An error occurred while saving the comment We'd like a bit of clarification on this, when the ask is to "allow the user to add items", would the list of items be pre-populated on the screen for users to select? If so, where would the list of items come from without querying the source and target?
-
1 vote
An error occurred while saving the comment How would Gearset programatically know what format (Metadata or SFDX source) to parse the repository with, other than using the "sfdx-project.json"? file?
-
2 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment Would the suggestion on https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/34803568-ability-to-chose-multiple-targets-for-a-deployment be a better way to address this use case?
-
1 vote
An error occurred while saving the comment The changed on and changed by information comes from the Salesforce Metadata API, when you compare it against an git branch, that information isn't available as it's the org that returns this information for Gearset to show you. I wonder how this could be achieved technically.
-
1 vote
An error occurred while saving the comment How wide would be considered big enough?
-
1 vote
An error occurred while saving the comment Hi Adah, Can you clarify what you mean by "fields" here? Do you mean Custom Fields on a Custom object? What if your comparison only contained Apex classes, what would be exported in that case?
-
4 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment Would would something like this help meet your need?
https://docs.gearset.com/en/articles/5432441-pilot-features-gearset-public-api
-
11 votes
An error occurred while saving the comment Would would something like this help meet your need?
https://docs.gearset.com/en/articles/5432441-pilot-features-gearset-public-api
-
1 vote
An error occurred while saving the comment I think the tricky thing would be the definition of "a component":
Would deploying 2 custom field permissions on the same profile X be counted as 2 components (custom field permissions) or 1 component (profile)?
Hi Paul,
Thank you for the feedback, I can see your point of view.
We have a challenge to communicate this planned outage to all our customers.
Last year, a few team’s users all chose to dismiss the notification, and therefore failed to be aware of the planned maintenance window, which severely impacted their planning. From talking to them and taking their feedback, we’ve chosen to make the banner not dismissible this year.
From your feedback, I sense we went too far. I will take more thought to see if there is a feasible middle ground to improve this situation for future communications.
Valerio Chang - Customer support and Documentation