Andrew on 01 Aug 2018 23:44:36
Incremental Refresh appears to only function for inserting the parameters into a Date/Time format.
What about where users are using DirectQuery, which does not allow us to change the format type of a column, and the SQL Server data being queried is only in Date format, not Date/Time?
Please allow parameters and incremental refresh to function as well for Date format columns.
- Comments (5)
RE: incremental refresh for date not just date/time
Please also add date time offset (the standard date datatype in OData v4)
RE: incremental refresh for date not just date/time
Support of Date in addition to DateTime is also critical for Datamarts, because Date format has a much better compression in Vertipaq than Datetime, and in a business - wich is the core of the Datamart audience - the info at the minute has much less value : the day is the perfect granularity.
RE: incremental refresh for date not just date/time
In most cases, a partition key is a DATE type. Please enhance the incremental refresh logic internally to handle both DATE type and DATE/TIME data type column.I'll buy you dinner, Christian :-).
RE: incremental refresh for date not just date/time
This is critical for users of SAP BW, as DateTime fields are not detected by the Power BI connector, and converting Date fields to DateTime in a subsequent step negates query folding and the benefit of using incremental refresh.
RE: incremental refresh for date not just date/time
As I was testing some more, am I wrong to think Incremental Refresh can be applied to DirectQuery? It is strictly limited to Import? What about Dual within the new Composite Model release though?