Forum Discussion
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 trying to connect to an existing semantic model in service and then use Translations Builder, receive the following: "PBIX projects with Live Mode Datasets Not Supported *YET*."
For those mature in their translation journey, what direction would you provide? Our team is feeling a strain between "adopt fabric, warehouses, direct lake semantic models, etc." and "but the semantic model needs to be local to desktop to use a tool like Translations Builder."
Thanks so much for any direction or lessons learned in this ever changing landscape!
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!
5 Replies
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.
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!
Hi mstearns,
Thank you for reaching out to Microsoft Fabric Community.
Thank you tayloramy for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
