Hi all,
I’m facing a delegation issue in Power Apps when filtering a Dataverse table on a DateTime column (cr437_financialyear).
🔹 Scenario
- Data source: Dataverse table
'New tables' - Column:
'Financial Year'(DateTime) - Example stored value:
12/31/2025, 12:00:00 AM - Control: Date Picker (
FinancialYearDateValue)
🔹 Problem
When I filter using direct equality:
'Financial Year' = FinancialYearDateValue.SelectedDate
👉 It does not return expected results, even when both values appear identical (12/31/2025).
However, when I use:
DateValue('Financial Year', "en-US") = FinancialYearDateValue.SelectedDate
👉 It works correctly, but triggers a delegation warning:
"The DateValue part of this formula might not work correctly on large data sets."
🔹 Full context (simplified)
🔹 Observations
- The DateTime values look identical in UI
- Suspecting timezone / hidden time component mismatch
- Using
DateValue()fixes comparison but breaks delegation
🔹 Questions
- Why does direct equality fail even when both values appear the same?
- Is this due to DateTime vs Date or timezone conversion (UTC vs local)?
- What is the best delegation-safe approach to compare a DateTime column with a DatePicker value?
- Would changing the Dataverse column to Date Only be the recommended fix?
- Is there any way to normalize the values without breaking delegation?
🔹 What I’m trying to achieve
Filter rows by:
- Client Code
- Status
- Matching Financial Year (based on DatePicker)
while remaining fully delegable.
Any advice would be appreciated. Thanks!

Report
All responses (
Answers (