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

    darkknight
    Expert ⭐️
    July 10, 2020

    @HollySimmons absolutely correct.  We have the same issue too.

    Jeff Kirkpatrick
    rakesh
    Gainsight Employee ⭐️
    Lets put your data to work!
    July 10, 2020

    Its completely understandable that we would want Label instead of GSID. Unfortunately the way our data models are, one would have to pick the label (do a join in this case) to get this today. That being said,

    1. We will consider this feedback and work on it to make sure Rules works with picklists more seamlessly. 
    2. If you want this specific to S3 export, do let us know; When we turn the toggle on, you would notice an additional field containing label  in addition to the S3 export you configured. 

     

    darkknight
    Expert ⭐️
    July 10, 2020

    @rakesh thank you.  Hopefully this gets priority.  The more we leverage MDA data the more crucial this becomes.  

    Jeff Kirkpatrick
    hardik_mota
    Helper ⭐️
    August 17, 2020

    Hi @rakesh 

    Once we turn on this feature, it adds an additional column in the S3 export of the picklist label. Do we have any plan to replace the IDs on the original columns themselves? We have customers who plan to read the CSV export programmatically. 

     

    Best,

    Hardik

    Hardik
    jean.nairon
    Expert ⭐️
    August 17, 2020

    @hardik_mota - that would be a much more ideal solution. Having a legend in a separate column is better than what is currently available. But this would be much easier if the IDs were replaced by the labels. 

    Jean
    hardik_mota
    Helper ⭐️
    August 19, 2020

    I agree with you, thanks @jean.nairon 

    Hardik
    rakesh
    Gainsight Employee ⭐️
    Lets put your data to work!
    August 21, 2020

    Hi @rakesh 

    Once we turn on this feature, it adds an additional column in the S3 export of the picklist label. Do we have any plan to replace the IDs on the original columns themselves? We have customers who plan to read the CSV export programmatically. 

     

    Best,

    Hardik

    We do not have it immediately on our plan to change this Hardik. But will keep this feedback in mind for any further enhancements

    cmultanen
    Helper ⭐️
    September 1, 2020

    Just ran into this issue with some customer journey-related data we are trying to export to our data warehouse. 

    darkknight
    Expert ⭐️
    January 27, 2021

    @rakesh @hardik_mota  I really hope this gets more attention.  Makes troubleshooting and confirmation so much more difficult. 

     

    Jeff Kirkpatrick
    keith_mattes
    Helper ⭐️⭐️
    January 27, 2021

    I added a +1 for this @darkknight , I feel your pain although I do not have any use cases that exacerbate this issue at the moment.

    Sr. Customer Success Operations Analyst/Gainsight Admin/Data Nerd