Skip to content

AdminGearset Team (Feedback Manager, Gearset)

My feedback

60 results found

  1. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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?

  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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!

  3. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    Hi David, I'm reaching out to you in the in-app chat to investigate this. Are you okay to respond there?

  4. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    AdminGearset Team (Feedback Manager, Gearset) supported this idea  · 
  5. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 
  6. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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.

  7. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    What if the custom git repository connection is for BitBucket or Azure Devops? Would a "View on GitHub" button make sense?

  9. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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

  10. 25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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?

  11. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    How would Gearset programatically know what format (Metadata or SFDX source) to parse the repository with, other than using the "sfdx-project.json"? file?

  12. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 
  13. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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.

  14. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    Thanks for the idea. Does connecting via the Custom git repository connection on the https://app.gearset.com/linked-service-connections page help address this use case?

  15. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    How wide would be considered big enough?

  16. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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?

  17. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    Would would something like this help meet your need?

    https://docs.gearset.com/en/articles/5432441-pilot-features-gearset-public-api

  18. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    Would would something like this help meet your need?

    https://docs.gearset.com/en/articles/5432441-pilot-features-gearset-public-api

  19. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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)?

  20. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminGearset Team (Feedback Manager, Gearset) commented  · 

    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.

← Previous 1 3

Feedback and Knowledge Base