Forum Discussion

jaryszek's avatar
jaryszek
Icon for Super User rankSuper User
8 months ago
Solved

Deploying model via tabular editor is not moving relationships views...

Hi Guys, I am using DirectLake over OneLake, and to copy the semantic model into another workspace, I am using the deploy feature there:   and it is working perfect but the issue is that I...
Need Help
  • Anonymous's avatar
    Anonymous
    8 months ago

    Hi jaryszek ,

     

    When deploying a semantic model through Tabular Editor using the XMLA endpoint the behavior you are seeing is expected and not a defect in your process. The deployment does move the actual relationships that define how tables are connected in the model and those relationships are fully functional once the model is deployed. What does not move is the visual relationship layout that you see in the model diagram view. That layout is part of the user interface experience in tools like Power BI Desktop or the Fabric portal and it is not stored in the semantic model metadata that XMLA exposes. Because Tabular Editor and other automation tools work only against that metadata layer they have no access to the diagram positions or saved relationship views and therefore cannot deploy them.

    This also explains why it can look as though relationships are missing even though reports continue to work as expected. The relationships are present and active but the diagram view has no saved layout to render them in a familiar arrangement so the UI appears reset. Recreating or rearranging the diagram is purely a visual step and does not change the underlying model. The same limitation applies to all XMLA based approaches including TOM scripts TMSL deployment notebooks using semantic link labs and deployment pipelines. None of these tools can move the relationship diagram because that information is simply not part of the model schema.

    In short there is no supported way today to migrate relationship views or diagram layouts between environments. Tabular Editor is already doing everything that is technically possible by deploying the full model metadata including tables columns measures and relationships themselves. Any manual adjustment you make afterward is only restoring the visual layout for convenience and does not indicate data loss or an incomplete deployment.

    Thank you.

cengizhanarslan's avatar
cengizhanarslan
Icon for Super User rankSuper User
8 months ago

Instead of using Tabular editor use the following code below in a notebook, it would be much more faster and simpler.

 

Step 1: Install semantic-link-labs

Run the following in a Fabric notebook:

 

%pip install semantic-link-labs

Step 2: Duplicate the semantic model

This step extracts the existing semantic model definition and recreates it as a new model in the target workspace.

 

# Source configuration
dataset = 'Model'
source_workspace = 'WS'
 
# Target configuration
new_dataset = 'Model_Import'
target_workspace = 'WS'
 
# Get the semantic model definition from the source workspace
model_bim = sl.get_semantic_model_definition(
dataset=dataset,
format='TMSL',
workspace=source_workspace,
return_dataframe=False
)
 
# Create the semantic model in the target workspace (Import mode)
sl.create_semantic_model_from_bim(
dataset=new_dataset,
bim_file=model_bim,
workspace=target_workspace
)

 

  • jaryszek's avatar
    jaryszek
    Icon for Super User rankSuper User
    8 months ago

    Thank you, will consider it in the future. For now, I want to stay with TE3. It is so powerfull and has so many additional features in comparison with Microsoft solutions...

    It is a possibility to use notebooks to only move Relationships views? Not entirely model? 

    Best,
    Jacek

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 months ago

      Hi jaryszek ,

       

      When deploying a semantic model through Tabular Editor using the XMLA endpoint the behavior you are seeing is expected and not a defect in your process. The deployment does move the actual relationships that define how tables are connected in the model and those relationships are fully functional once the model is deployed. What does not move is the visual relationship layout that you see in the model diagram view. That layout is part of the user interface experience in tools like Power BI Desktop or the Fabric portal and it is not stored in the semantic model metadata that XMLA exposes. Because Tabular Editor and other automation tools work only against that metadata layer they have no access to the diagram positions or saved relationship views and therefore cannot deploy them.

      This also explains why it can look as though relationships are missing even though reports continue to work as expected. The relationships are present and active but the diagram view has no saved layout to render them in a familiar arrangement so the UI appears reset. Recreating or rearranging the diagram is purely a visual step and does not change the underlying model. The same limitation applies to all XMLA based approaches including TOM scripts TMSL deployment notebooks using semantic link labs and deployment pipelines. None of these tools can move the relationship diagram because that information is simply not part of the model schema.

      In short there is no supported way today to migrate relationship views or diagram layouts between environments. Tabular Editor is already doing everything that is technically possible by deploying the full model metadata including tables columns measures and relationships themselves. Any manual adjustment you make afterward is only restoring the visual layout for convenience and does not indicate data loss or an incomplete deployment.

      Thank you.

      • jaryszek's avatar
        jaryszek
        Icon for Super User rankSuper User
        8 months ago

        Thank you. Ah it is a pity!!