August 2025 works, September 2025 breaks with KeyNotFoundException in TableInputToQueryMap

[GiovanniVB1971]

Working on a power bi semantic model, connected to several tables (122) from 11 semantic models, some dataflows and a couple of ad-hoc tables created using some dax code. All works flawlessly in Version: 2.146.1454.0 64-bit (agosto de 2025), but as soon as I try to update to september 2025 version, this error appears:

Error Message: "The given key was not present in the dictionary."

It seems to me that the error occurs in Power BI's internal table mapping code. Something is wrong with this version.
I tried also July 2025 version an all works just fine. Please fix whatever is causing this problem in september 2025 versions.

[v-karpurapud]

Hi @GiovanniVB1971 

We wanted to follow up and ask if you have submitted a support ticket. Could you let us know if the issue was resolved after creating the support case?If you have any further questions, please let us know. we can assist you further.

Regards,

Microsoft Fabric Community Support Team

Best regards,

Community Support Team.

[GiovanniVB1971 · Accepted solution]

Hello, after updating to version 2.148.878.0 the problem seems to be solved. I just did a couple of tests and it's working fine; There is no problem importing new tables from different semantic models.

[v-karpurapud]

Hi @GiovanniVB1971 

Thank you for the update.

[lbelow]

I have the same issue and ask this to be resolved for the September Desktop release.
It is very painful to uninstall the September version and reinstall the August version.

[GiovanniVB1971]

Thanks @lbelow for sharing your experience. I lost a full day trying to isolate the problem in several tables. One by one, eliminating those tables and trying to import a data flow or a table of another semantic model. And as you say, it is very painful to return to the August version after all these tests, I hope Microsoft can solve this error soon.

[v-karpurapud]

Hi @GiovanniVB1971 and @lbelow 

Thank you both for sharing your experiences. We understand how frustrating and time-consuming it is to troubleshoot across multiple tables, only to find the issue is specific to the September 2025 release. Reaching out to Microsoft Support is the best way forward, as this will allow the product team to review the problem directly and work toward a resolution.

Regards,
Microsoft Support Team.

[v-karpurapud]

Hi  @GiovanniVB1971 

Thank you for sharing these details. Based on your description, your model works as expected in the July and August 2025 versions, but encounters issues in the September 2025 release. This aligns with reports from other users following the September update.

As the issue may be related to changes introduced in the September 2025 release, we recommend reaching out to Microsoft Support for further analysis and assistance.

In the meantime, continuing to use the August 2025 version should ensure your models operate without interruption.

You can submit a ticket through the Microsoft Power BI Support Portal:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Regards,
Microsoft Support Team.