Skip to main content
brijesh
Contributor ⭐️⭐️⭐️
Nov 1, 2016 5:05 PM UTC

Preserve/replicate configuration for MDA after Salesforce sandbox instance is refreshed

We do frequent Salesforce sandbox refreshes and with refreshes we needed to reconfigure rules/report which are based on MDA Object.

With this idea - i am proposing some automation to replicate configurations from production into sandbox once sandbox is refreshed.

    10 replies

    darkknight
    Expert ⭐️
    Nov 1, 2016 5:59 PM UTC
    Adding on to this...had a similar situation happen when we spun up a developer sandbox.  Usage Measures did not display in  Usage Configuration yet when I tried to create them it said they already existed.

    From support: 
    "when you spin off another instance, it will carry over all the custom fields that are setup on the backend in SFDC. We don't, by nature auto map those for you which is what the feature request would be in this case."
    Translate
    Jeff Kirkpatrick
    praneet
    Helper ⭐️⭐️⭐️
    Nov 7, 2016 5:11 PM UTC
    Hi Brijesh,
    We are currently developing functionality called Cross Org migration(Available in beta), where the next set of steps is to help you replicate MDA objects and rules and reports associated to it. I will update this thread with release information once we are close to it.
    Translate
    Feb 7, 2017 5:38 PM UTC
    So if we refresh our sandbox (deleting our Gainsight data) we could copy production rules/reports back into the sandbox at a later date? Is that what this functionality would do?
    Translate
    praneet
    Helper ⭐️⭐️⭐️
    Feb 27, 2017 4:12 AM UTC
    Hi All, 
    With Gainsight 5.5/Winter Release, users will have ability to migrate custom MDA collections/object along with ability to migrate Reports and Rules on them.
    However on Rules front we have following limitations, we only support following actions - Create CTA, Set Score(1.0), Load to Customers, Load to Usage, Load to SFDC and Load to Relationships.
    We are working on supporting more actions for Rules migration.
    Translate
    todd_atkinson
    Contributor ⭐️⭐️⭐️
    Mar 2, 2017 8:59 PM UTC
    Thought this might help those following this conversation about the Migration Tool.

    Read more here: "Migrating Schema and Assets from a Source Org to a Target Org"

    Oh, and be sure to read up on Bionic Rules to learn how you to move your MDA data between SF Orgs by Exporting Data to an S3 Bucket, "Export to S3 from Bionic Rules".
    Translate
    brijesh
    brijeshAuthor
    Contributor ⭐️⭐️⭐️
    Mar 10, 2017 4:58 PM UTC
    MDA Migration does not work properly if field has lookup set.
    Translate
    brijesh
    brijeshAuthor
    Contributor ⭐️⭐️⭐️
    Jun 26, 2017 2:38 PM UTC
    @Praneet - is there any new enhancements to cross migration functionality
    Translate
    brijesh
    brijeshAuthor
    Contributor ⭐️⭐️⭐️
    Jan 18, 2018 7:23 PM UTC
    @Praneet - this is really causing issues for us as we do frequent refreshes on sandbox environment
    Translate
    dstokowski
    Gainsight Employee ⭐️⭐️
    May 4, 2018 7:58 PM UTC
    We have a partial solution now vetted for this.  First, you must know your SFDC Org ID prior to refresh and your SFDC Org ID post refresh.  After the refresh, you need to authorize MDA for the new SFDC org.  Then submit a ticket to Gainsight Support and we can repoint your existing Sandbox MDA to your refreshed org.   LMA access is desired so we can verify success for this.
    Important note:  The data in MDA will not be refreshed from Production - it will be the same data that was in your Sandbox.  If you made any other schema or MDA changes in your MDA Production, you would need to migrate these. 

    We are planning to address a full solution sometime in the second half of this year.
    Translate
    pgeorge
    Gainsight Employee ⭐️
    Gainsight Employee ⭐️
    May 7, 2019 10:07 AM UTC
    The self sandbox management is a part of our roadmap. We are working to bring in sandbox managment to the admins

    Translate