Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
BatuhanOzgun
Regular Visitor

The operation could not be completed because there was a problem updating the Dataflow.

after "Save & Closer" i got this;

The operation could not be completed because there was a problem updating the Dataflow. The Dataflow is being updated by another operation.

 

after "Retry" i got this. 

Operation could not complete because a newer version of this dataflow was saved since you started editing.

 

After these i pressed edit tables and i can see the data in table, but if i import table to power bi desktop table load empty.

 

 

is anybody solved this problem

2 REPLIES 2
BatuhanOzgun
Regular Visitor

Hi @collinq,

I did everything you said, I didn't even bother, I created my work in the error-prone workspace from scratch in a new workspace. (With the new documents and tables, it had no connection to the first workspace) Still, I got the same error.

 

Then I created a third workspace in the same way. The difference from the first and second workspace is that I did not create tables with the "Enter Data" function, instead, I created them in Excel and added the Excel documents to the dataflows. Now I am working smoothly in the third workspace I created. (Of course, I wasted about 10 days for the first two)

 

Here I need to explain that, when the error first appeared, after setting up the entire structure, I was adding new rows to a table created with the "Enter Data" function. After adding rows, I got this error when I "Save and Close" Dataflow. This table was a table in which I mapped customer name information from two different systems. For this reason, it was flowing all over the workspace.

 

While creating the dataflows in the second workspace, I entered single rows of data into the problematic table I mentioned at certain stages, and I did not encounter any problems, but after the work was completed, I pasted 20 rows of data into the same table and received the same error again.

 

Here I think the table I created with the "Enter Data" function is causing a problem;

1- There was a language-specific character in the data I sent (data in Turkish language), which caused a problem.
2- Although the table was small, my transactions in subsequent tables were so large that it somehow caused an error in the update process.
3- It's not my expertise, but I think this function creates a bug during the dataflow update phase.

 

For myself, I am currently proceeding by taking care to establish a structure in which I do not do any data entry in Excel/SharePoint or Power BI. If I need to add intermediate tables, I definitely use Excel and have never encountered this problem again.

Thank you for your interest,

collinq
Super User
Super User

Hi @BatuhanOzgun ,

 

You have to go back through the process.  Maybe you had two tabs open with the same thing?  That message that it is in another operation usually means that it was refreshing while you were editing, or it was saving while running, or you (and/or others) had it open in edit mode in more than one place, or it was using another dataflow or data source that was actively running.  

 

The fact that you got no data output makes sense - that is because it failed while running so it "clears itself".

 

So, make sure you do not have it open and that it is not running.  Then, open it , edit it (even if that means just opening and then hitting save).  Then refresh it.  Then you should see your data.

 




Did I answer your question? Mark my post as a solution!

Proud to be a Datanaut!
Private message me for consulting or training needs.




Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.