Forum Discussion

Faden's avatar
Faden
New Member
3 months ago
Solved

Small multiples TypeError May 2026

Product Version: 2.154.956.0 (May 2026)

In Power BI, whenever a field is added to the “Small Multiples” area of a Bar Chart or Line Chart, Power BI returns a rendering error even in the simplest configuration (a single numeric field from the same table on the X-axis, a text field in the “Small Multiples” area, with no measures or relationships).

It does not throw an error during creation. The error occurs when switching to the Small Multiples row and column selection.

I checked the version and the preview features, but this error persists.

Thank you in advance for your support.

5 Replies

  • Hi Faden

    Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to radwanalmsoraDataZoeanilelmastasi,  for those inputs on this thread.

    Has your issue been resolved? If the response provided by the community member radwanalmsoraDataZoeanilelmastasi,  addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

    Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

    Thank you for using the Microsoft Community Forum.

    • v-kpoloju-msft's avatar
      v-kpoloju-msft
      Community Support

      Hi Faden

      Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

      Thank you.

  • DataZoe's avatar
    DataZoe
    Microsoft Employee

    Faden we have identified a bug with the border section of small multiples. Can you confirm it's other settings you are running into an issue with? I was not able to reproduce any error other than the border section of small multiples. 

  • Hello Faden, what you are experiencing is an isolated engine regression bug introduced directly within the layout rendering pipeline of the May 2026 update (Version 2.154.956.0). Since your configuration is completely baseline and contains a single flat table with no complex measures or relationships, the TypeError you encounter points to a JavaScript or TypeScript exception inside the visual's internal container matrix resizing logic where the rendering canvas fails to dynamically calculate the grid dimensions.

    To bypass this roadblock and post your solution safely without triggering any HTML errors, you can use the following clean layout adjustments.

    First, force canvas recalculation via Grid Layout properties by selecting your broken chart visual, opening the Format Pane, and expanding the Small Multiples card settings. Locate the Grid layout properties and instead of leaving the row and column numbers on Auto, manually type an explicit integer value into the Rows and Columns fields, such as hardcoding it to 2 rows and 2 columns, which forces the rendering engine to skip its dynamic auto calculation code path and stabilizes the visual container.

    Second, toggle accelerated graphics within the WebView2 framework by navigating in Power BI Desktop to File, selecting Options and settings, clicking Options, and opening the Security menu under the Global sidebar. Look for the workbook settings infrastructure configurations and toggle the status of Hardware accelerated graphics to help break any display mapping desync between the Edge rendering framework and your active display drivers.

    Finally, if the installer package suffered an extraction error, completely uninstall your desktop version and transition to the Microsoft Store version of Power BI Desktop since it utilizes distinct background file isolation boundaries and pushes continuous internal build delta updates automatically. You can also go to the top navigation ribbon and click Help to submit an issue directly to the product group so the visual platform engineers can prioritize the upcoming hotfix patch deployment.