Anyone having their list record appearing and disappearing this past day? I didn’t change any configuration and see this happening. I doubt that the appsheet team is pushing updates this weekend but just wonder
This list would appear once, then disappearing when I resync the emulator or mobile app 3 times in a row, then reappear… I can’t figure out what could cause that.
Here’s the list expression:
Solved! Go to Solution.
and(
WEEKNUM([End Day]) = WEEKNUM(TODAY()),
[Sharing] = “Public”
)
I would actually create a field inside the class logs table to hold the WEEKNUM([End Day]) value;
Then use that slice in a Ref_Row() formula for the gym;
You can then take this list and use that inside your SELECT(), instead of your double-dipped version. (^_^)
You could go a step further and include the part about their points not equaling zero (in the slice), this would then give you only the class logs with progress, for that week, for that gym, that are public.
The problem might be caused by the progress bard from quickchart.io that do not have enough time to load completely and prevent the rest of the html to load correctly…
What do you think @tsuji_koichi?
your formula having a select inside a select inside a select
@MultiTech_Visions Beautiful isn’t? lol
Table definition:
As you see I simply want to show the list of students from a specific gym that trained this week and order them by points collected (see screenshot). Basically dynamically show a scoreboard.
Is there a simpler way to do? I can’t see an alternative without having the ability to create a join table (Join of Class Logs and User Profiles).
and(
WEEKNUM([End Day]) = WEEKNUM(TODAY()),
[Sharing] = “Public”
)
I would actually create a field inside the class logs table to hold the WEEKNUM([End Day]) value;
Then use that slice in a Ref_Row() formula for the gym;
You can then take this list and use that inside your SELECT(), instead of your double-dipped version. (^_^)
You could go a step further and include the part about their points not equaling zero (in the slice), this would then give you only the class logs with progress, for that week, for that gym, that are public.
interesting. I would need to add the gym column in the class logs table to add the ref_row. So basically adding a slice, list field with ref row, duplicate the gym field into 2 tables to get rid of 2 selects in a field expression. Is this considered a better design or coming up with workaround to make it work with Appsheet?
I spend quite some time doing similar workarounds and wonder if it is worth it. It makes the app more complex to maintain since I often asked myself why I have this or that slice, field or action in the app.
UPDATE
I added the gym column on the Class_Logs table, created the slice but didn’t created the ref row field. Working well so far! Thank you @MultiTech_Visions
This is the preferred design - at least IMHO.
User | Count |
---|---|
40 | |
34 | |
29 | |
23 | |
17 |