Skip to main content

October v5.19 Release Highlights Video

  • October 10, 2018
  • 13 replies
  • 107 views

lila_meyer
Forum|alt.badge.img+5
To learn more about release v5.19 that's coming out on Oct. 16, check out this 8-minute overview video or the draft release notes:

13 replies

jivesh_upadhyay
  • Contributor ⭐️⭐️⭐️
  • October 10, 2018
Thanks for the enhancements in the V 5.19 release. The improvements to the migration process are a good start. Although, we need a migration tool which is more stable and user friendly. Hope your team is working on it. Looking forward to the future release.

matthew_lind
Forum|alt.badge.img+11
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • October 11, 2018
I may have just done a Happy Dance.

Retaining the schedule on rules switched to Inactive / Pausing a Rule is going to be awesome!

dan_ahrens
Forum|alt.badge.img+2
  • Expert ⭐️⭐️⭐️
  • October 12, 2018
Hi Jivesh,

Yes, we are still doing a ton of development work on our migration tool. We just couldn't wait to let you try these new features, so we released them while we continue work on the other features! 🙂

lila_meyer
Forum|alt.badge.img+5
  • Author
  • Gainsight Employee ⭐️⭐️⭐️
  • October 16, 2018
The final published release notes are available now!

jivesh_upadhyay
  • Contributor ⭐️⭐️⭐️
  • October 16, 2018
Thanks Lila Meyer.

darkknight
Forum|alt.badge.img+5
  • Expert ⭐️
  • October 23, 2018
1000 times yes!

darkknight
Forum|alt.badge.img+5
  • Expert ⭐️
  • October 23, 2018
Lila, in the release notes regarding X-Org Migration it states:

"New Dropdown Data Types can now be migrated through X-Org Migration Tool: Picklist/Multipicklist under Schema (Both Standard and Custom), and URL Datatype can now be migrated using the X-Org Tool. For more information about how to migrate Single Select and Multi Select Picklist, refer to the Corss-Org Migration article." (Typo, btw)

When I look at that referenced article, it appears to be talking specifically about Dropdown fields in MDA Standard or Custom tables.   Do you know if this includes fixing the issue where Salesforce picklist fields get migrated but the VALUE doesn't?

lila_meyer
Forum|alt.badge.img+5
  • Author
  • Gainsight Employee ⭐️⭐️⭐️
  • October 25, 2018
Hi Jeff, welcome to the new Community!

Regarding your question, Salesforce picklist fields cannot be migrated with the Cross-Org tool. The enhancement in 5.19 was for migration of MDA picklist fields.


darkknight
Forum|alt.badge.img+5
  • Expert ⭐️
  • October 25, 2018
Lila are you saying SF picklist fields can't be migrated "right now" but will be in the future?

That's a pretty big gap if there aren't plans to include them.


lila_meyer
Forum|alt.badge.img+5
  • Author
  • Gainsight Employee ⭐️⭐️⭐️
  • October 25, 2018
I'll have to check with the product team, Jeff. I'm not sure about roadmap for this.


darkknight
Forum|alt.badge.img+5
  • Expert ⭐️
  • October 25, 2018
Thanks. What is not getting migrated today are actually Gainsight picklist items that live in Salesforce, like Call to Action::Type, Call to Action::Reason, Call to Action::Status - you'd think those would migrate.



The work around is to use the free text options like Reason Name, CTA Type Name and Status Name - but A) I don't want to have to go back through and invasively change all my rules and 😎 I can do "includes/excludes" with picklists when there are multiple options I want include/exclude.

Other items, like Customer Info picklist fields seem to migrate fine.

Let me know if this needs to be submitted to support.


darkknight
Forum|alt.badge.img+5
  • Expert ⭐️
  • December 31, 2018
Hi Lila - did you ever get an answer on this? Thanks!


lila_meyer
Forum|alt.badge.img+5
  • Author
  • Gainsight Employee ⭐️⭐️⭐️
  • January 2, 2019
Checking back...stay tuned!