New Topic

Community Topic Problem Report Builder

Category Report Builder

Product Version 7.2

Chart Values' Sorting Problem

Tal Mickel shared this problem ago

Defect Fixed

Hey

There's a problem with the alpha-numeric sorting.

See the picture below. It's suppose to be 1 to 17 but it sorts all that begin with '1' first, and others later.

Thanks!

Dor & Tal

0c5c9114e8d3ef86bdab7026fb34b736

The same problem 0

Best Answer

Guest ●

Hi Tal,

Just a quick update, this issue is fixed in the next release of Yellowfin (EoM July 2017)!

Upgrade one the release is available and you should no linger have this issue!

Best regards,

Pete

Replies (3)

Guest ●

Hi Tal,

This is expected behaviour as the field is a Text field (not numeric) and is doing Lexicographical sorting.

You could get around this by removing the "Tier" text and converting ot a number and then using a label "Tier" for the key.

I hope this helps,

Best regards,

Pete

Reply URL

Guest ●

Hi Tal,

There is another way to do this too: by setting up an Org Reference code for the Tiers - this will allow you to specify the order of the codes and how it's displayed:

here is a video that should explain it for you:

https://www.youtube.com/watch?v=8k3093theT0&feature=youtu.be

And a wiki article on the use of Org Ref codes:

http://wiki.yellowfin.com.au/display/USER73Plus/Reference+Code+Use

I hope these help!

Best regards,

Pete

Reply URL

Tal Mickel ●

Thank you for your solutions !

I'm familiar with the Org Ref solution, but on the user side its problematic.

Lets take for example the VIP tiers. Our users sees "Tier 3" and wants to filter on that value.

When you create an Org Ref, behind the scenes it does not change the value. The value changes only on the visual level. So the true value is 3. But when the user will use 'Tier 3' - it will not show anything, because its not the true value.

URL

Guest ●

Hi Tal,

Let me know the solution that you decide to use in the end :)

Have a great day,

Pete

URL

Guest ● ●

Hi Tal,

Just a quick update, this issue is fixed in the next release of Yellowfin (EoM July 2017)!

Upgrade one the release is available and you should no linger have this issue!

Best regards,

Pete

Reply URL

Sagar Vavhal ●

Hi Peter,

Do we have any YF defect number for this? I would appreciate if you can share the same

Thanks

Sagar

URL

Guest ●

Hello,

The defect ID is: YFN-6085

Best regards,

Pete

URL