Power Platform Community Forum Thread Details

Has anyone else experienced this? My Power Apps connects to Microsoft Fabric SQL Analytics Endpoint via DirectQuery. The published app works flawlessly - zero errors, perfect data display, users love it.

BUT - Power Apps Studio shows "JSON parsing error, expected 'string' but got 'number'" on every control. Can't demo the editor to stakeholders without them thinking the platform is broken.

Tried:
- Removing/re-adding data source
- Clearing cache
- Different browsers
- Explicit CAST on all SQL columns
- Simplified views

Nothing fixes the Studio error, but published app = perfect.

Help appreciated!

Categories:

Building Power Apps

Hi @MJ-18021022-0,

You’re using Power Apps + Microsoft Fabric SQL (DirectQuery).
Published app → works perfectly.
Power Apps Studio → shows: “JSON parsing error” on every control.

This means Studio is choking on metadata coming from the Fabric SQL DirectQuery connection, even though the runtime handling it fine.
This is not a data problem (you already CASTed everything), but a Power Apps Studio parsing bug with Fabric SQL’s metadata JSON.

Not sure, this might be a bug in Power Apps Studio’s schema resolver for Fabric SQL DirectQuery.

Did you try various methods of casting? If not, can you give a try?
CAST(field AS VARCHAR(50))
CONVERT(VARCHAR(50), field)

SELECT field = CONCAT('', field)

Create a view in Fabric SQL that converts every column to a consistent type (prefer NVARCHAR).
Reconnect Power Apps to that view.
This almost always fixes Studio-only JSON parse bugs in DirectQuery scenarios.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.