Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Using PBID June 2025.
I tried to filter a date column but the parameters did not show RangeStart, RangEnd until I flipped the field from date to datetime.
Should it be possible on date only?
Thanks
w
Solved! Go to Solution.
Hi, datetime data type is the correct type.
However, if you can try to create a function in Power Query editor that converts to datetime data type to number type (for date_key column in fact tables) or date type (date column in fact tables), then I think you can implement in a way that you expected.
Thank you.
Configure incremental refresh for Power BI semantic models - Power BI | Microsoft Learn
Hi @UncleLewis ,
Thanks for reaching out to Microsoft Fabric Community.
As mentioned by @Jihwan_Kim , Power BI requires the column used for Incremental Refresh to be of datetime type at the filter step for RangeStart and RangeEnd to bind properly.
If your source table only has a date column or uses integer surrogate keys in yyyymmdd format, you'll need to convert the RangeStart and RangeEnd parameters accordingly by creating a function to map the datetime values to match the format used in your table. This is particularly useful when your fact table uses surrogate keys instead of native datetime columns.
You can refer to the Convert DateTime to integer section in the official documentation for that approach.
Configure incremental refresh for Power BI semantic models - Power BI | Microsoft Learn
Hope this helps. Please reach out for further assistance.
Thank you.
Hi @UncleLewis ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.
Hi @UncleLewis ,
We wanted to kindly follow up regarding your query. If you need any further assistance, please reach out.
Thank you.
Hi @UncleLewis ,
Just checking in to see if you query is resolved and if any responses were helpful.
Otherwise, feel free to reach out for further assistance.
Thank you.
Hi @UncleLewis ,
Thanks for reaching out to Microsoft Fabric Community.
As mentioned by @Jihwan_Kim , Power BI requires the column used for Incremental Refresh to be of datetime type at the filter step for RangeStart and RangeEnd to bind properly.
If your source table only has a date column or uses integer surrogate keys in yyyymmdd format, you'll need to convert the RangeStart and RangeEnd parameters accordingly by creating a function to map the datetime values to match the format used in your table. This is particularly useful when your fact table uses surrogate keys instead of native datetime columns.
You can refer to the Convert DateTime to integer section in the official documentation for that approach.
Configure incremental refresh for Power BI semantic models - Power BI | Microsoft Learn
Hope this helps. Please reach out for further assistance.
Thank you.
Hi, datetime data type is the correct type.
However, if you can try to create a function in Power Query editor that converts to datetime data type to number type (for date_key column in fact tables) or date type (date column in fact tables), then I think you can implement in a way that you expected.
Thank you.
Configure incremental refresh for Power BI semantic models - Power BI | Microsoft Learn
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 39 | |
| 37 | |
| 33 | |
| 33 | |
| 29 |
| User | Count |
|---|---|
| 132 | |
| 90 | |
| 78 | |
| 66 | |
| 65 |