Both replies are pointing in the right direction but there's a simpler path for your specific setup.
Since your Session Date column is Date Only (not DateTime), you don't actually need the TimeZoneOffset adjustment. Date Only fields in Dataverse don't store time or timezone info, so the UTC conversion adds unnecessary complexity and can actually introduce bugs when the offset pushes the date over midnight.
The cleanest fix is DateValue() on both sides to make sure you're comparing just the date part with no time component noise.
For Circle2_1 Visible property:
CountRows(
Filter(
Bookings,
DateValue(Text('Session Date', "mm/dd/yyyy")) =
DateValue(Text(DateAdd(_firstDayInView, ThisItem.Value, TimeUnit.Days), "mm/dd/yyyy"))
)
) > 0
Note: use mm/dd/yyyy not dd/mm/yyyy in the Text() format string inside DateValue(). Power Apps DateValue() expects month-first format regardless of your display preference.
For Gallery1 Items property:
Filter(
Bookings,
DateValue(Text('Session Date', "mm/dd/yyyy")) =
DateValue(Text(_dateSelected, "mm/dd/yyyy"))
)
And make sure your MonthDayGallery OnSelect sets the variable:
Set(_dateSelected, DateAdd(_firstDayInView, ThisItem.Value, TimeUnit.Days))
The most common reason none of your previous attempts worked is almost certainly the dd/mm/yyyy format string in DateValue(). That's a silent failure — no error, just no matches.
Best regards,
Valantis
✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.
❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).
🏷️ For follow-ups @Valantis.
📝 https://valantisond365.com/
