Skip to content

Kevin Hong

← Gearset

My feedback

2 results found

  1. Update Metadata Change Monitor Report

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Help us improve Gearset » Monitoring and reporting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Kevin Hong shared this idea  · 

  2. Add support for deploying a name change to a SFDC component (such as profile)

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Help us improve Gearset » Comparisons and difference visualization  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Kevin Hong commented  · 

    We have run into the same issue and have found a workaround to address this, not ideal. From a tooling perspective, this seems like a big challenge especially if you want to persist the name change to git source control (i.e. you don't have a metadata ID to compare in this case, only the file name which has now changed. Trying to do any sort of hash or some deterministic approach is also tricky if aside from the rename the profile was also updated. I think if salesforce includes some sort of unique identifier in the metadata xml, it could be possible and gearset take the appropriate action to rename the file then perform a checkout, update, commit, something to that effect. Would love to see how this problem can be tackled by the gearset team.

    Kevin Hong supported this idea  · 

Feedback and Knowledge Base

(thinking…)