Forum Discussion

ASD85's avatar
ASD85
Frequent Visitor
5 years ago

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 ...
Need Help
Anonymous's avatar
Anonymous
Not applicable
5 years ago

Following up on my previous answer... If you have translations for your dimensions, than you have to place them directly in the dimensions AS COLUMNS, not separate rows. This way all your would-be "many-to-many" will be eliminated. Then, you can create views of the cube/model in which you'll hide the columns you don't need. People then should connect to the view they want based on their language.

  • ASD85's avatar
    ASD85
    Frequent Visitor
    5 years ago

    Creating copies/views of the model on a per-language basis is in my back pocket in the event that there's absolutely no other solution to this issue. That was actually the very first idea that I pitched to my client, but they are adamant about having a single report from a standpoint of simplifying both development and maintenance.

     

    We are migrating their current reporting from Qlik, and Qlik handles this issue seamlessly via the ability to add conditional statements to practically any object in a report, so it would be a difficult conversation to tell them that this functionality they've utilized for years in their old solution is not available in the new solution that they're investing a lot of time and money into.