TRUE/FALSE Filter No Longer Working?

[mykrobinson]

Did something recently change with how Appsheet handles Yes/No data types?

I have a small app the clinic uses to track appointment reminders where patients cancelled through the automated call system. Front desk staff uses the app to make sure they don’t miss calling a patient back to reschedule, since the automated system also ties in with our EMR and takes them off the schedule if they cancel.

Anyways, the app has been working until recently, so that when a patient entry is marked as “complete”, they are moved to a different view when [comple]=true, with the unprocessed cancellations being in a different view.

For whatever reason, that filter/slice is no longer working properly and some completed entries are still showing in the unprocessed view.

Any ideas what is going on here??!

[Suvrutt_Gurjar]

You may want to recheck your column type and in test pane.

A quick testing shows that it should perfectly work. results of a slice filter expression below.

However you could write [Complete]<> TRUE also simply as NOT([Complete])

Since Y/N columns anyway evaluate to TRUE or FALSE, a further comparison with TRUE or FALSE is redundant.

[mykrobinson]

I tried that, and the problem persists. This is all just a bit strange because it was working fine for weeks then did this unexpectedly without me having changed anything

[mykrobinson]

to test a bit further, i even tried changing the slice for Complete to ISNOTBLANK([Complete]) and Unprocessed to ISBLANK([Complete]) and it still shows in the same fashion

[Steve]

Sounds like a bug or corrupt configuration. Please contact AppSheet Support for help with this.

[mykrobinson]

done, thank you.

[Suvrutt_Gurjar]

Great. May we also request you to post back what was the issue and solution, as and when you solve it?

[mykrobinson]

They are claiming it is working as it should, so i did a screen recording with voiceover to show them that it clearly is not.

[Suvrutt_Gurjar]

Thank you for the update..

[mykrobinson]

this is resolved. Apparently, i made a mistake in some apps script in the dataset and was accidentally creating some duplicates.

I needed to change the scheme i was using for dynamic key creation. I was using a timestamp and appointment type, but the issue was that there can easily be patients in different locations with an appoint at the same time and date and of the same type, so i have included the patient MRN with the primary key for the records to prevent this going forward.

[Suvrutt_Gurjar]

Thank you very much @mykrobinson for the update. Really appreciate it.

[mykrobinson]

to add a bit more context, i dump a report from our EMR to an intermediate spreadsheet to compare to the live data set and merge the differences. The script runs the key creation and handles the comparison and subsequent merger.

So i had instances where even though they were two different patients, the key was not unique, and this caused the anomalies in the UI. The filter was working exactly as prescribed, its just that i would have one that was complete and one that was not, with the same key.