Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes in TE3 are not saved in PBI Desktop despite using the Save button etc. #1438

Open
Oleks23 opened this issue Feb 3, 2025 · 2 comments
Labels
template: issue Issue report created by user, needs to be triaged

Comments

@Oleks23
Copy link

Oleks23 commented Feb 3, 2025

Description

Hello, I am sure this has been asked before but...

Quite often the updates that I make in TE3 are not saved in PBI Desktop - I have been pushing hard on the synchronization icon.

Very often it just stops working (saving) and I am not aware if the changes have been saved in PBI.

Could someone advise what I could do here?

Thanks.

Tabular Editor 3 Version

6258

Screenshots

No response

Steps to Reproduce

No response

Expected behavior

No response

Crash Report

No response

Windows Version

No response

@Oleks23 Oleks23 added the template: issue Issue report created by user, needs to be triaged label Feb 3, 2025
@otykier
Copy link
Collaborator

otykier commented Feb 4, 2025

This is an issue on the Power BI Desktop side. As far as we can tell, it happens when the XMLA payload reaches a certain size (typically when the model contains many objects). You can try the workaround discussed here.

An alternative solution is to add a dummy table to your model, or just use a table that doesn't contain a lot of data / is quick to refresh. Then, every time after you hit "Save" in Tabular Editor, switch over to Power BI Desktop, and refresh that table. This should make the field list in Power BI Desktop update, so that you can see any changes made from Tabular Editor.

@Oleks23
Copy link
Author

Oleks23 commented Feb 4, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
template: issue Issue report created by user, needs to be triaged
Development

No branches or pull requests

2 participants