Language of "Other" segment in charts

Hi Daniel,

Thanks for your question.

I've had a play around with it in version 9.5.1 of Yellowfin, and simply changing the language of the User changes the 'Other' segment. There is no need to set a translation value for it, as it should change the value based on the User's language preferences.

In the example above, I've changed my language from English to Spanish on the Profile Settings page and I am seeing the appropriate value.

Let me know if this is what you are experiencing.

Kind regards,

Simon

Hi Simon,

Thank you very much for your support.

In our YF version (8.0), the name of the "Other" segment is not changing, although German is selected.

Has this been implemented in newer versions of Yellowfin or is possibly only German not affected in case of different user languages?

Best regards,

Daniel

Hi Daniel,

This is definitely a possibility, would you mind letting me know which version of Yellowfin you are using by navigating to your /info.jsp page?

Then, I can go ahead and attempt replicating it on my end.

Kind regards,

Simon

Hi Simon,

the /info.jsp shows the Application Version 8.0.8. Do you need more information or is that all you need to know?

Best regards,

Daniel

Hi Daniel,

That's OK, that's all the information I needed and it helps so that we can keep this post public for the benefit of the rest of the Community. I have confirmed that this is the case in version 8 and I'll go ahead and change this into an Idea to be considered as an Enhancement Request. It is likely that this is a feature that cannot be backported in version 8 due to the major changes in version 9, so I would suggest upgrading to version 9 for this functionality.

Before becoming a request, ideas will be reviewed by our Product Team and chosen for Enhancements based on feasibility, level of positive impact to the user experience, and votes from the community.

I will update this post with any future information relevant to this process.

Kind regards,

Simon

Hi Simon,

Thanks for your support. Updating to version 9 will hopefully solve this issue.

Best regards,

Daniel