TMDL View

[DevisSs]

 I'm working with TMDL View, very easy operations like put measures in a folder or something like that. It happens that the after pushing "Apply" on TMDL View, if I try to save the file an error message arise:

"Non è possibile salvare il documento" stand for it is not possible to save the document. What figure out under that string is that the path in which my pbix file is stored is not valid. 
Generally, this error arise when I start to work in the View. You may say " why don't you use a project to work with TMDL?". The error arise as well. Tryied! Above all, apply changes it Trasform data in PBI is a lot much faster in pbix than in pbip so for a matter of efficiency I switched on pbix, but this is another problem.
Some suggestion?

[MFelix · Accepted solution]

Hi @DevisSs ,

I was not able to reproduce this error, but I believe that the best option is for you to place the question on the errors part of the forum since it will be redirected at MSFT team that can check this type of errors.
https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues

If you have any news on this please let me know-.

[Anonymous]

Hi @DevisSs ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[Anonymous]

Hi @DevisSs ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[Anonymous · Accepted solution]

Hi @DevisSs ,

Thank you for reaching out to the Microsoft Fabric Community. Also thank you @miTutorials and @MFelix  for your insights.

The error you're encountering "Non è possibile salvare il documento" due to an invalid file path typically arises when the file path becomes corrupted or inaccessible during the session. This can happen in scenarios where:

• The file was moved, renamed, or deleted externally after opening it in Power BI.
• TMDL View introduces structural changes that conflict with unsaved PBIX metadata.
• Special characters or restrictions in the directory path interrupt the save process.

Since you’ve already tested both .pbix and .pbip formats and confirmed the issue persists, here are a few suggestions to work around this:

• Before applying changes in TMDL View, try using "Save As" to a different local directory (e.g., C:\Temp\) to eliminate path-related issues.
•  Ensure the PBIX file is not stored in OneDrive/SharePoint-synced folders during editing, as sync conflicts can also cause this.
• Occasionally, permission restrictions on certain folders can block file writes. Try running Power BI Desktop as an administrator.
• If you're working with .pbip, make sure the metadata and model folder hierarchy remains intact, especially after manual edits.

Hope this helps. Please reach out for further assistance.

If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.

Thank you.

[Anonymous]

Hi @DevisSs  ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[miTutorials]

Take a look at my video explaning about TMDL - I hope this helps.

Unlock the Power of TMDL in Power BI | 9 Game-Changing Use Cases | MiTutorials

[MFelix · Accepted solution]

Hi @DevisSs ,

I was not able to reproduce this error, but I believe that the best option is for you to place the question on the errors part of the forum since it will be redirected at MSFT team that can check this type of errors.
https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues

If you have any news on this please let me know-.