Forum Discussion
Modeling multiple many-to-many relationships based around a language component
I have a scenario where a few of my dim tables include translations for field values into multiple languages. In each table, the native key is the combination of a language key and a code value. For ...
Here's another one but from the comments below the issue that Ruth talks about has not yet been rectified (and nobody knowns if it will ever be).
I think I've actually come across this video already. The visual headers aren't really a concern because we're already doing metadata translations through the XMLA endpoint. As far as changing the values with parameters, I don't think that's even an option for end users in an app, is it? It would also necessitate a dataset refresh I believe, and that would be a dealbreaker.
I think the closest I could get to something like this would be passing through parameters in the report URL, but I'm not sure whether those persist once the user starts navigating to other pages.