Hi @Stuart thanks for sharing this feedback. I will share this with the team and soon get back to you on the ETA.

Hi @shambhawi,

Looping back on this because the issue appears not only to be limited to the relationship stage values appearing as the GSID, but any dropdown/picklist field shows as the GSID instead of the value shown in the UI.

This is a pretty poor UX; part of the appeal of HRE (in my opinion) is the improved ability to test and iterate while building out solutions.  As far as I can tell there is no way to see what the GSID values are for stage dropdown values, or any other dropdown.  So for example, if a rule uses a case field based on stage values it’s pretty difficult to evaluate if the case field outputs are as expected because we only see the GSID not the dropdown value shown in the UI.

Any idea if this will be resolved as a hotfix or rolled into an upcoming release?

Thanks!

Hi @Stuart, I have consulted with my team, in the data prep flow we have a workaround for this.

In the data preparation step, if a dropdown/picklist field is used, we offer an alternative by duplicating the field and converting it into a string. By doing this, you will be able to view both the GSID and its corresponding string value.
 

Let me know if this helps ? 

For now, this is not possible for the Single Object Flow, we will implement this soon for the Single Object Flow as well.

I have run into this one recently as well.  What I find very confusing is that the pass file is different depending if you run the rule as a test or if you run it for real.  

When you run it as a test, the column headers are a mix of “gsd….” names and actual column names.  You also don’t appear to get the resolved values on look ups, but rather the source field.  

When you run it for real, you get better column names and you get the resolved look up values like you expect.  

It would be very helpful if you can update the test run pass file to match how it is when it runs for real.  

It would also be helpful if there was a table or anything exposed that would allow admins to query the dropdown values.  So when logs show the dropdown GSID values, we could still look them up.  

Hi @john.cowles Thanks for this feedback, this was an issue with Bionic rule as well for the test run, we will take this as an enhancement for the Horizon rule.