Skip to main content
cameron_wright
Gainsight Employee ⭐️⭐️
January 7, 2019
New Idea

rule results different from preview data

  • January 7, 2019
  • 35 replies
  • 587 views
After talking with a customer via a support case we discovered that when you preview the results of a rule they will not show the same as the results show.

For instance, in the first image below you see a preview data set to a rule, this shows the name of the data in the field. "Guided" is an example.

But in the second image this is a rule run result and it shows an ID (blanked out for privacy purposes).

This is as design but in the future myself and others would find it useful for these to be matching. Troubleshooting a rule or data validation is very hard when these do not match up.

The reason it is like:

The execution itself uses the actual data so we have GSID's for Picklist values in the logs.

But in rule setup preview we are converting these GSID's to Picklist names to avoid confusion while setting up the rule.

The way we would like it to work:

Show the datasets as the same so that we can validate and confirm data easily.





    35 replies

    jitin_mehndiratta
    Helper ⭐️⭐️⭐️
    January 22, 2019
    Hi Cameron,

     

    I agree with you that the rule results and preview results should be consistent. There need to be some design level change to make this happen and we are exploring ways/options to achieve the same. The timelines are not known yet. I will keep you posted on the same.

    Regards,

    Jitin

    darkknight
    Expert ⭐️
    March 13, 2019
    Probably goes without saying, but this also applies to exports of the data. I just created a rule to map Customer Info to Company and wanted to pull Status from both, but the Status field from Company exports the GSID for that dropdown value, not the value itself. And I cannot figure out how to map the GSID for that Status to the actual value



    Jeff Kirkpatrick
    darkknight
    Expert ⭐️
    April 2, 2019
    @jitin_mehndiratta Any update on this?

    This is already a pain for us, but will become an even BIGGER pain as we want to be able to export data from Gainsight to S3 that will be picked up via Informatica for inclusion in our data warehouse.

    We have to have the ACTUAL data - not an ID.

    Jeff Kirkpatrick
    darkknight
    Expert ⭐️
    April 3, 2019
    @dan_ahrens this really needs a solution ASAP. Since we're having to create Bionic Rules to supplement reporting gaps, we need to be able to export the actual values not long IDs.

    cc: @kelly

    Jeff Kirkpatrick
    darkknight
    Expert ⭐️
    July 7, 2020

    @minh_phan may you please follow up on this?  This is a frustrating problem that incredibly slows me down as an admin:

     

     

    Jeff Kirkpatrick
    minh_phan
    Gainsight Employee ⭐️⭐️
    July 7, 2020

    @rakesh PM for Rules

    phani_kumar
    Gainsight Employee ⭐️⭐️
    July 8, 2020

    Hi,

    I also faced the same issue. But we have a workaround for this, i.e using “Case” expression to get the Value instead of IDs.

    Rule Result Screenshot:

     

    So Used the Case Expression to convert the Ids to Actulal string.

    Screenshot:

    So after the Case Experssion below is the result screenshot:

    Hope this workaround will work will helps you to get the Actual Field values instead of Ids.

    Thanks.

    rakesh
    Gainsight Employee ⭐️
    Lets put your data to work!
    July 9, 2020

    @darkknight For S3 exports, we do have a toggle which will export values in addition to GSID’s. Let me know if you want to try that.

    cc: @swaroop_badam  

    darkknight
    Expert ⭐️
    July 9, 2020

    @phani_kumar thanks for the workaround, but that just requires extra work on the part of the admin.  It needs to do the logical translation to save us time and effort.

     

    @rakesh I would like to know more about this - but ultimately everything should export/translate the actual value and not the GSID.

    Jeff Kirkpatrick
    HollySimmons
    Helper ⭐️
    July 10, 2020

    This issue also means we cannot filter the actions based on certain picklist values, and instead have to filter on the GSID of the picklist value. 

    I have a number of GS → SF rules which I include filters to ensure updates are only done if the source and target data differ (to prevent unnecessary writes) but it always passes the filter because it’s comparing Source: GSID against Target: Value which will never match.