You are trying to get the following list:
The list of Tasks that are:
- The Task is NOT complete. (Field Complete is “no”)
- OR the Task may be complete (field Complete is “yes”, but only if it has been completed “today” (whatever that means… we will get to that)
Once we have that list, you just want to show the first 5 as they would appear when sorted by “Order” (which indicates their importance).
Let’s examine these criteria and see how we can model them in Bubble… and see if we can do this with a constraint that we could put on the Search, so that we download as little extraneous data as possible to the browser (rather than having to filter a big list in the browser):
Note: When we do a Search in Bubble, we can apply multiple constraints, but these constraints are logically ANDed together. We have no way of ORing constraints in the Search’s constraint dialog.
When we examine the idea above, we see that we want to return Tasks whose status may be Complete or not Complete. So it seems that we would not attempt to constrain on “Complete”. (Complete being a boolean, any basic constraint we do here will leave us with ONLY Tasks that are Complete OR Tasks that are not Complete. But not both.) But we want both (for certain cases).
So the question is: Is there any other difference between a Complete Task and a not Complete Task. Yes, yes there is: a Complete Task will have a non-empty Completed_On date. A not Complete Task will have an empty Completed_On date. This is good. Let’s remember this.
Let’s turn to the idea of Complete Tasks. It is OK for our list to contain them if and only if they were completed “today”. How do we determine this? There are two ways:
Date-wise comparison: A task must have been completed “today” if its Completed_On date is greater than the starting point of today. The starting point of today is this:
Current date/time change hours to 0 change minutes to 0 change seconds to 0
Task's Completed_On > Current date/time change hours to 0 change minutes to 0 change seconds to 0, the Task was completed today. (Note that time only moves in one direction – forward – so we do not need to check if the task was completed before the end of today. If such a Task exists, that task is from the future and we should be very very spooked right now.)
Task's Completed_On < Current date/time change hours to 0 change minutes to 0 change seconds to 0 the Task was completed before today. (Again, there is no such thing as a Task completed after today. Such a task would be from the future.)
Text-wise comparison: If we want to know whether two date objects (which are of course date/time objects) happened on the same day, we can compare just the “calendar date” parts as text and see if they are identical. Like:
Task's Completed_On:formatted as mm/dd/yyyy is Current date/time:formatted as mm/dd/yyyy
^^^^ Note: Both :formatted as operators must be configured identically.
AT THIS POINT, I’M GOING TO SHORTCUT THINGS A BIT…
I did some testing here and while we can evaluate an empty date against a non-empty date, this seems not to be the case in a Search constraint.
For example: Suppose that Some_Task’s Completed_On is empty (it is a null date). This expression will evaluate to “yes” in a text element:
Some_Tasks's Completed_On < Current date/time (just as an example)
… and conversely the > condition will evaluate to no.
It seems like we could use this fact to construct a constraint that passes what we want regardless of whether Completed_On is empty or not, but it seems we cannot. (Oh foo!) If we could, we might be able to do this in just one slick Search.
When we use that as a Search constraint – regardless of whether we “ignore empty constraints”, no Task with an empty Completed_On date will pass such a constraint. It’s not entirely clear to me why, but this approach is a non-starter!
Example: A constraint set up this way…
… only returns Tasks that have a non-empty Completed_On date. This seems like a bug given what we know about the behavior of a similar expression in a text element. This example, BTW, yields the following in run mode:
Even though I have Tasks in my sample app that have empty Completed_On dates, they simply will not appear here, regardless of the “Ignore empty constraints” setting in the constraints dialog.
But we CAN get the Completed tasks that happened today using this technique. So that’s good. And of course not Completed tasks are just Do a Search for… Tasks where Complete is “no”.
SO, CAN WE DO IT TEXTWISE?
- Well, we can’t do the textwise date comparison in the constraint as we can’t turn Completed_On into text there. So not helpful. (But aren’t you glad to know about this method of determining if two dates/times occur on the same day?)
SO… IT SEEMS WE MUST COMBINE TWO SEARCHES OR USE THE FILTER:ADVANCED OPERATOR
So, unless we want to download ALL Tasks to the browser and process them there (we don’t really want to do that if we can avoid it), we need to combine two lists. Two lists of the same type can be combined using the :merged with operator.
So, we know a way to get Completed tasks that happened today. That Search is like this:
In my sample app this yields just the Tasks that are complete but where completion happened today:
Now let’s get the Tasks that are NOT complete:
Now let’s combine those:
^^^ the first search has the “Completed_On > start of today” condition. The second Search has the “Complete = no” condition.
This yields a list of Tasks that got completed today combined with a list of Tasks that are not completed, as we expect:
NOW: YOUR app has a concept of “order”. So, in YOUR app, you would (1) not sort either of these searches in the constraint dialogs – cuz that doesn’t matter. (2) append a :sorted operator to this combined search that sorts these the combined list by order. I don’t know what your order represents so that’s up to you how that works. But in my example, I’m just going to sort them by Created Date descending so you can see how the expression looks (where mine says “Created Date” yours would say Order):
Now you want to truncate that list just to the first five entries. There are two ways of doing that:
If you are displaying this list in an RG, you could just force the RG to be a fixed number of cells set to 5.
However, if you want to truncate the underlying list (so that, for example, your RG could be any style), you add the
:items until operator like this:
And there you go.
Now, a caveat: You seem to be SEARCHING FOR ALL TASKS. This of course is fine as you’re developing your app. But note that in a multi-user app, obviously, you want a constraint everywhere in this example of something like “Created by = Current user” right? Because of course you don’t wanna mix up MY Tasks with YOUR Tasks. I’m assuming you get this, but FYI.
(Aside: such a constraint is not necessary if you have a privacy rule set up that allows only the Task’s creator to see their tasks, but for clarity of your programming I would still have that. But that’s just me.)
The sample app I futzed around with and grabbed snips from, is this page in my Timezoner demo app. (The editor is viewable by all.)
Here’s the run mode:
And here’s edit mode for this page:
Since I believe that this is actually the most performant and scalable way to do this particular search, I’m not going to show how you would do this with Do a Search for… Tasks (unconstrained):filtered (and then with Advanced set in the dialog and an expression), but you could explore that on your own now that you grok some new concepts. (The bad thing about :filtered – if you do it client side / in the browser as we would be doing here – is that ALL tasks will get downloaded to the browser and then the filter operation will be performed by the browser. This is wasteful.)