'The base version must not be negative when impact is requested for a transaction. '.

[mibu]

Hi Everyone,

I am simply trying to pull in a simple dimension Excel file...  like I have done many times before...  and am getting the following error message:

Failed to save modifications to the server. Error returned: 'The base version must not be negative when impact is requested for a transaction. '.

Pls let me know if you have had any experience with this error message.

Thanks!

mibu

[mibu · Accepted solution]

Hi @jagatho,

Thanks so much.  Your feedback gave me the idea to Match Exactly the headers of the Excel Dimension file I have been trying to load…  with the corresponding column of the Cube to which I am connecting.  In previous attempt where I got afore mentioned error message, they were not named identically, not even close.

Naming columns identically in both files…  allowed Power BI to load the Excel Dimension file without an error message.  Funny, it did not autodetect the relationship between the newly named column in my Excel Dimension file and corresponding column in Cube.  No matter…  I was able to create the relationship manually, Close & Apply, and again, no error message.  I am back up and running.

Again, thanks so much for your feedback…  it spurred the thought that lead to a solution.

Very best,

mibu

[Anonymous]

I run into this problem yesterday and found the solution on StackOverflow.

In File, Options, Current File, Data Load, Relationships disable Autodetect new relationships after data is loaded.

 

[mibu · Accepted solution]

Thanks @Anonymous!  I appreciate the feedback.

I also found that Deleting all rows under last line of data in table...  and deleting all columns to the right of last column of data in table, eliminated the error message and allowed Refresh to occur.

best,

mibu

[Anonymous]

I got the same error, after so many attempts i tried by changing relationship from 'both' to 'Single' and error gone. this is not I want. but as there is no other solution.

we are using PBIRS Sept 2019 version.

[jagatho]

It has to do with the auto detection of relationships.

If I remove the column that would make sense that Power BI would predict having a relationship between tables and added a new one with the same name with null values in two PowerQuery steps, then I can load the data.

After the initial load I can remove the two steps and everything works, because it only tries to detect relationships on the initial load.

[mibu · Accepted solution]

Hi @jagatho,

Thanks so much.  Your feedback gave me the idea to Match Exactly the headers of the Excel Dimension file I have been trying to load…  with the corresponding column of the Cube to which I am connecting.  In previous attempt where I got afore mentioned error message, they were not named identically, not even close.

Naming columns identically in both files…  allowed Power BI to load the Excel Dimension file without an error message.  Funny, it did not autodetect the relationship between the newly named column in my Excel Dimension file and corresponding column in Cube.  No matter…  I was able to create the relationship manually, Close & Apply, and again, no error message.  I am back up and running.

Again, thanks so much for your feedback…  it spurred the thought that lead to a solution.

Very best,

mibu

[v-chuncz-msft]

@mibu,

Check this post and create a support ticket if necessary.

[mibu]

Hi @v-chuncz-msft,

I removed the filters from the source Excel file and continue to get the same error message, attached.

[Shwetha_ps]

Restart your device

[mibu]

I have created a support ticket and will advise if I get an answer.

[Anonymous]

Hi Mibu,

Was a resolution provided for this error?  I just received this today. 

Thanks,

Meg

[mibu]

Hi @Anonymous, check out last post in thread for a possible solution. best, mibu