TMSL Synchronize command not working with Premium Per User datasets (wrong documentation?)

[StevenVDP]

Hi everybody,

for one of our customers, we are investigating if we can bring their on-prem tabular models to Power BI datasets hosted on Premium Per User workspaces. The current on-prem setup includes seperate query & process instances and a TMSL synchronize command is executed to sync the model between instances.

Based on the documentation (see here), the TMSL synchronize command also applies to Power BI Premium. But when trying to sync the model from one PPU hosted workspace to another PPU hosted workspace - we receive the following error: "This operation is not supported by the Power BI Premium product".

As the error message is quite clear, I am wondering if the documentation is wrong or whether this only applies to datasets backed by Premium Per Capacity?

An additional question: the process/query sync script is still a remnant from their old multidimensional setup (it was migrated to tabular on-prem a while back). Is a similar setup still necessary for tabular/Power BI? In other words, if the model is refreshed (or a part of the model), will the users experience timeouts or idle queries? Please note that over 40 users query the model concurrently during dataset refresh.

Thanks!

[StevenVDP]

Hi, thanks for the reply!
I did check all the settings and they seem to be properly configured.

In the meantime I have tried the XMLA sync script on datasets hosted on an Embedded capacity (instead of PPU) and I receive the same error message ("This operation is not supported by the Power BI Premium product").

My gut feelings tells me that this is not supported in Power BI (in general) yet - but that consequently means that the documentation here is wrong.

[v-xulin-mstf]

Hi @StevenVDP,

Is your issue solved?

If the issue has been solved, please adopt your solution to help others.😉

Best Regards,
Link

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[StevenVDP]

Hi @v-xulin-mstf ,

unfortunately, it is not solved yet :-). We believe the documentation is wrong as the message clearly states (when we run the sync command) that this feature is not available for Premium datesets. I'll check to raise a support ticket to get some confirmation.

[v-xulin-mstf]

Hi @StevenVDP,

Okay, looking forward your reply.

Best Regards,
Link

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[v-xulin-mstf]

Hi @StevenVDP,

The latest documentation does not indicate that this feature is not supported.

Please summit a support ticket for help.

Best Regards,
Link

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[v-xulin-mstf]

Hi @StevenVDP,

About dataset connectivity with the XMLA endpoint, please refer:

https://docs.microsoft.com/en-us/power-bi/admin/service-premium-connect-tools

Please try the following steps and check:

• Enable Read Write for XMLA Endpoints at your Premium Capacity.
  In the Admin portal, select Premium Per User.
  Expand Workloads. In the XMLA Endpoint setting, select Read Write.
  
• Enable Read Write for XMLA Endpoints at your Premium Capacity.
  
• Enable the Export data setting in the Power BI Admin Portal.
• Make sure your localhost is compat level 1500 or use the Integrated Workspace Mode.
• Delete any role memberships in your model during the public preview.
• A write operation on a dataset will prevent it from being downloaded back as a PBIX file.

Best Regards,

Link

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.