Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
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.
User | Count |
---|---|
64 | |
27 | |
25 | |
17 | |
11 |