How to move field parameter into One Lake Remote Semantic Model?

[jaryszek]

Hello,

I want to use Tabular Editor to move field parameter from my report in import mode into Remote OneLake semantic model.

Subscription Hierarchies Switcher = {
    ("NormalizedResourceName", NAMEOF('Fct_EA_AmortizedCosts'[NormalizedResourceName]), 0),
    ("ResourceType", NAMEOF('Fct_EA_AmortizedCosts'[ResourceType]), 1)
}

This is a parameter which i need to move into OneLake semantic model. 

I saw migration labs link functions (LINK) but I do not want to use it. I just want to create table, maybe in Dax, whataver and switch it to field parameter...
Can anybody explain process step by step? 

Best,
Jacek

[v-ssriganesh]

Hi @jaryszek,
Thank you for reaching out to the Microsoft fabric community forum. To add your field parameter to the OneLake semantic model without migration tools, do this:

• Use Power BI Desktop to connect to your Fabric workspace’s semantic model.
• Create a field parameter and test it in a slicer to ensure it switches fields correctly. Save it and publish the report to your Fabric workspace.
• In the Fabric workspace, if possible, add a new calculated table to the semantic model with the same DAX as your parameter or use DAX Studio to connect to the model and create the table with your DAX.
• Refresh the semantic model in Fabric. Check in a new report that the parameter appears and works in visuals and remove the parameter from the original report if it’s now in the semantic model to avoid duplicates.

Check your workspace allows model edits. If the parameter doesn’t work, an admin may need to adjust settings with a tool like DAX Studio. Keep the table simple for Direct Lake mode.

Best regards,
Ganesh Singamshetty.

[jaryszek]

There is no way to build a field parameter in One Lake Remote Semantic Model. Option is disabled. 

I found workaround from Tabular Editor:

https://www.youtube.com/watch?v=Cg6zRhwF-Ro 

Best,
Jacek

[v-ssriganesh · Accepted solution]

Hi @jaryszek,

Thanks for sharing the workaround. Since creating a field parameter directly in the OneLake semantic model is disabled, the Tabular Editor method from the video you found is a great solution. We appreciate your contribution and this will help other community members resolve similar issues more efficiently.

Best regards,
Ganesh Singamshetty.