Copy Hierarchies, Descriptions, and Relationships from Default Semantic Model to New semantic model

[jisaac]

Hello,

I have a Lakehouse for Gold layer in medallion architecture containing Fact and Dimension tables. Many of the Dimension tables like DateDim and CustomerDim will be used in different categories of reporting, i.e. Sales, Promotions, and Stock. I have taken advantage of the Model layouts feature in the automatically created Warehouse (SQL analytics endpoint) to create relationships, edit Sort by column's, add Description's, and add a Hierarchy to some Dimension tables. Is it possible to create a New semantic model from the Warehouse and include the Relationships, Descriptions, Hierarchies, and Sorts of the chosen tables from the Model layouts tab? 

My situation is that I want to create separate semantic models for different users' interests. Sales would have the sales tables, Shipping would have the stock tables, etc. I don't want to have to recreate all of the Relationships, Descriptions, Hierarchies, and Sorts for each separate model using the same tables. If it is not possible to copy these settings between semantic models, does anyone have an alternate solution to how I can handle my situation?

Thanks,

Jacob

[R1k91 · Accepted solution]

i think you should take a look to Tabular Editor. It's an external tool able to Connect to xmla endpoint of a model and to perform scripting. You can create a new model and read the original programmatically and replicate there relationships, measure and everything with basic c# scripting.

https://docs.tabulareditor.com/te3/features/csharp-scripts.html

for your needs it could be enough the free version but this is not capable to create a fabric model (you have to create manually  and then modify it with scripts). The paid one is able to create the fabric model too.

[jisaac]

It is unfortunately a premium solution, but it does look like a powerful tool to do what I need to. Thanks for the info!

[Anonymous]

Hi @jisaac ,

When creating a new semantic model in the SQL endpoint corresponding to lakehouse, it is possible to choose which tables to include, but there is no way to replicate these settings mentioned in your description between different semantic models, they need to be reconfigured manually, which can be a bit of a pain, but there doesn't seem to be any other solution as far as I know.

If anyone else has a better solution please share it at the bottom of this thread.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!