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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Bug with September 2023 Version - DAX & CALCULATED COLUMNS NOT WORKING

Dear MSFT

 

Recently I've noticed that calculated column and dax measures s are going blank or unchanged after writing code.

 

Can you review this potential bug from September version? 

 

Thanks.

Status: Investigating

Hi  all,

 

Power BI released a new version on September 25th, please update to the latest version to see if the problem still exists.

 

Best regards.
Community Support Team_Caitlyn

Comments
dsalony
Helper I

hello.  came to this forum to report the same glitch with the Sep'23 release.  i had to uninstall the Sept desktop version, load the July release, at which point when i entered the same DAX into a column i was setting up, it immediately showed me that i had created a circular logic error that i easily fixed... the Sept release doesn't provide that context, it just blanks out the column after you input the DAX

davidgsmith
Regular Visitor

I'm having this issue. Type in a formula and it just reverts to previous one. If a new column then just goes back to column =.

I made sure everything was up to date.

I've tried restarting app and pc.

I installed the Aug version of Power BI, now there's a circlular reference with a column that has since been deleted. Even if I use a version before the ghost column was created.

o59393
Post Prodigy

Hi @davidgsmith 

 

Thanks for sharing, happens to me the same.

 

Just one question, do you think the circular reference is valid or is an error of Power Bi too?

davidgsmith
Regular Visitor

They are sepertate lookupvalue formulas that don't reference each other.

Thought it might be related to having a calculate(Max()) in the lookupvalue but removing that is still the same issue.

Deleting the column keeps the error but refers to it as a key ID instead, the column doesn't seem to delete.

The circular reference doesn't seem valid to me after trying various things, and can't even delete the column it keeps mentioning.

o59393
Post Prodigy

Thank you @davidgsmith 

 

So we are having the same issue. I used the July version and it keeps showing me a circular dependency error even though I am sure there isn't one.

 

 

 

 

gabrieljaeger
New Member

Hi everyone,
I had the same issue here. All measures that are related in a calculated column can't be changed .
After edit its automatically returns to initial code without any error message.

v-xiaoyan-msft
Community Support
Status changed to: Investigating

Hi  all,

 

Power BI released a new version on September 25th, please update to the latest version to see if the problem still exists.

 

Best regards.
Community Support Team_Caitlyn

o59393
Post Prodigy

Hi @v-xiaoyan-msft 

 

I did a test and now the code won't dissapear/undo or revert it to "Column = "

 

Now it will display "A circular dependency was detected". From my point of view it doesn't seem a valid error.  I tried with a calculated column with related function (from 1 to many) and it will display me that message.

 

Other example is a dax measure within a calculated column. It keeps saying circular dependency even though I modified my dax measure to just a "1" to see if the error would go away from the column.

 

Thanks.

 

davidgsmith
Regular Visitor

I updated to Sep version and all day I've had no issues with DAX formulas dissapearing or cirular references that don't exist.

GarethW
Frequent Visitor

I am getting a similar error, but even weirder.

I have a calculated column that is using a MIN(Date) function with a filter for >= NOW(), which works fine, and stays when I save the PBIX.

I then tried to create a similar column, but using MAX(Date) with a filter of < NOW(), and whilst it populates the column with the correct data, as soon as I save the PBIX, that column reverts to just a name without the DAX formula.

Even weirder, I tried pasting the EXACT same DAX from the first calculated column (wondering if the change to MAX was the issue), and it populates the data matching the original calculated column, but STILL removes the DAX when I try to save.