Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I'm getting an error when trying to push a refresh through an On Premise Gateway from the App Service, no errors are encountered when initially publishing the source pbix from Desktop.
UPDATE
1 - Removed "Changed Type with Locale" query module from both the primary table and the derived table(s), published ok, and refreshed ok.
2 - Reapplied "Changed Type with Locale" on the derived table, published ok, and refreshed ok.
3 - Reapplied "Changed Type with Locale" on the parent table, removed from the derived table, published ok, refresh failed as before.
The upstream provider provides date columns in two formats - Mode A that I need to migrate away from returns a string of mm/dd/yyyy - which PBI readily transforms to Date, publishes ok, and refreshes ok, and Mode B, which is in English European format of dd/mm/yyyy. PBI Desktop requires a Date with Locale transformation on Mode B date strings, and that seems to be where the problem lies.
Point of clarification:
A primary source dataset does support setting a specific column to "Changed Type with Locale"; this can be published and refreshed.
A secondary table derived from that converted column will block the dataset from being refreshed in the App service.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.