May 2024 Report Server Does not support Maxtrix Layout options in May 2024 Desktop for Report Server

[InTheDark]

We recently upgraded to May 2024 for Power BI Report Server (both server and desktop software) and we're running into a bug. Maxtrixes are not allowing us to use the Tabular or Outline formatting when published. They look fine in desktop, but once published on the server, they look like the default Matrix layout (compact). I submitted a forum post about this issue with images here: https://community.fabric.microsoft.com/t5/Report-Server/Matrix-Format-Changes-When-Published-to-Powe... 

I'm including the link because this page is not allowing me to upload all the images. Other users on that thread were also able to recreate the issue. 

If you use an older version of the Desktop for Report Server (like January 2024), turn off stepped layout on a matrix, then save it to the May 2024 Report Server, the formatting is maintained. I think the actual server is still looking for that stepped layout option, but the associated desktop software is using the new Tabluar/Outline/Compact language. 

[InTheDark]

Just an update. My coworker looked into the actual behind the scenes code using the instructions at the link below and identified the missing property using a January 2024 PBIX file. When he added the property to the May 2024 file, the chart showed correctly. Presumably, this should be a different property in the May 2024 desktop, since there are now more layout options, but the old property still works. 

https://community.fabric.microsoft.com/t5/Desktop/Modifying-the-Layout-file-that-is-embedded-in-a-pb... 

[Anonymous]

Hi @InTheDark ,

We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

Best regards.
Community Support Team_Caitlyn

[Msndrs86]

We are experiencing this too , having to caution team and refresh from server and avoid manual interventions / use a group of users on an older version to correct.

Any updates to when a fix might be deployed?

[AnupamaMatta]

This issue is affecting our reports very badly, Is there an ETA by which this issue is resolved ?

I could see another release happened on July 12th.  However, nothing is mentioned about the issue in changelog.  Does this release fixed the issue ?