Power Platform Community Forum Thread Details

I have an app that is live, right now, working. It has been working for years at this point.

When I go to edit the app, core functionality does not work. Namely, everything that attempts to hit a table in our Azure MS SQL database and filter on ANY kind of date column.

The connections are showing as valid.

If i create a gallery and point it at a table, it works fine.

If i filter that table by simple things like int's or bools, it filters fine.

If I add any condition on the "WorkedDate" column, everything gets screwed up.

The WorkedDate data type is datetimeoffset(7) because that's what I was told to do eons ago when I created this to get powerapps to play nice and not have to sprinkle all sorts of crazy logic everywhere. I have tested with normal Date column tables, and get the same results as detailed below.

Examples:

This works, returns data, hits the gallery:

Filter('AUDIT.FBCountSheet', ValidRecord = true && Location = varMasterNumber)

This returns nothing, note I've added WorkedDate as a filter. I have 100% confirmed that worked date and selected date are identical to powerapps, and have even use DateTime() in place of selected date to EXACTLY match the record, and it returns nothing:

Filter('AUDIT.FBCountSheet', ValidRecord = true && Location = varMasterNumber && WorkedDate = DateWorkedDate.SelectedDate)

This, returns an error "Data returned by the service was invalid". The only change between this code and the previous is instead of "WorkedDate =" as the filter, it's "WorkedDate >". I have no idea how this is even possible that it can run the first example, and return blank on the second, and error on the 3rd.

Filter('AUDIT.FBCountSheet', ValidRecord = true && Location = varMasterNumber && WorkedDate > DateWorkedDate.SelectedDate)

I have made 0 changes to this app between the last time it worked and now. Has there been some breaking change to powerapps?

Categories:

Building Power Apps

So making a brand new app with the exact same gallery, connection, and so on, works. I have no idea what's going on at this point, but it looks like i'm going to have to recreate the entire app from scratch if my export/import doesn't work.

Edit-

Welp.....i "fixed" it.

In the main app I created a new screen with just a gallery and tested the most basic of filters on date + location. It worked. I then went back to the screen that had been returning invalid data whenever I put a date filter on it. Works now.

So uh...yeah? I won't be surprised when this chokes again but at the same time it seems "make a new screen, set up a gallery, and use that connection" is a viable solution despite being totally insane? I control the data end to end on this (including the SQL database) so I'm positive nothing changed on the connection side, but oh well. At least I don't have to remake the whole thing at this moment.

Certainly another reason I'm going to look into migrating to custom webapps though. Really not acceptable behavior for a production application.