Forum Discussion

mstearns's avatar
mstearns
Regular Visitor
9 months ago
Solved

Semantic Models and Cultures

Hello -    We are in the process of making a number of our reports be multi-cultural. We're able to use a tool like "Translations Builder" on semantic models that are in import mode. However, when ...
Need Help
  • mstearns's avatar
    mstearns
    9 months ago

    Thanks for the reply tayloramy That's a fair suggestion to connect to the SQL endpoint and still leverage fabric that way. I could go the import route though I am trying to avoid that (trying to maintain all of my semantic model in the service. I am especially trying to avoid import because I'm wanting to take advantage fo direct lake automatic refresh from Fabric Warehosue to Fabric Semantic model. I wish there were a way to add cultures in Fabric to a semantic model connected via direct lake to a warehouse.

    I found another option through "Metadata Translator" that allows me to connect and add cultures to semantic models housed in the service. 

    I think I'll go that route as it can still connect to Azure Transltor Service. For translations beyond the meta data I'll download a trimmed semantic model to desktop, make my translations via Userculture and a locale table and republish. Then through deployment pipelines adjust the deployment rules to turn that "sample" filter OFF so that full data is flowing in production.

     

    Let me know if you see any issues with this.

     

    Thanks again for your reply!

tayloramy's avatar
tayloramy
Super User
9 months ago

Duplicate post of Language Cultures and Microsoft Fabric - Microsoft Fabric Community

Hi @mstearns, 

 

This is the challenge with adopting new cutting edge tools, third parties need time to update things. 

 

What I think you can do now is still use Fabric warehouses and lakehouses, but connect using the SQL endpoint and use Import mode. Not the best for performance/resource management in Fabric, but still pretty good. 

 

Then it is a normal semantic model and your third party tools should work.

 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

mstearns's avatar
mstearns
Regular Visitor
9 months ago

Thanks for the reply tayloramy That's a fair suggestion to connect to the SQL endpoint and still leverage fabric that way. I could go the import route though I am trying to avoid that (trying to maintain all of my semantic model in the service. I am especially trying to avoid import because I'm wanting to take advantage fo direct lake automatic refresh from Fabric Warehosue to Fabric Semantic model. I wish there were a way to add cultures in Fabric to a semantic model connected via direct lake to a warehouse.

I found another option through "Metadata Translator" that allows me to connect and add cultures to semantic models housed in the service. 

I think I'll go that route as it can still connect to Azure Transltor Service. For translations beyond the meta data I'll download a trimmed semantic model to desktop, make my translations via Userculture and a locale table and republish. Then through deployment pipelines adjust the deployment rules to turn that "sample" filter OFF so that full data is flowing in production.

 

Let me know if you see any issues with this.

 

Thanks again for your reply!

  • tayloramy's avatar
    tayloramy
    Super User
    9 months ago

    Hi mstearns, 

     

    That seems like a reasonable plan. 

     

    If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.