Posts: 24
Threads: 17
Joined: Jun 2022
Reputation:
0
I have a simple app (LUTO-RNAJ), or "Tracker". It has a database table of events. When the "Display" screen is. opened (e.g. by clicking "Show past events" on the home screen), the table is refreshed and then sorted.
It displays correctly in Appli on my Mac, but the same table is not properly sorted when I use the Appli player on IOS.
btw - using the "column sorting" button in the table header does produce correct sort order.
(This post was last modified: 05-07-2024, 12:20 PM by
alextweedly.)
Posts: 8
Threads: 0
Joined: Jun 2022
Reputation:
0
Hi alextweedly,
Thank you for providing your app code. I tested on my iOS device. After clicking on the "Show past events" button, I see a table sorted by the datetime column. The values are sorted in the following order: 12:47, 12:47, 12:48, 12:48, 13:07, 13:09, 14:21. What is the expected sort?
Posts: 8
Threads: 0
Joined: Jun 2022
Reputation:
0
Ah ok. I see from the sort icon that the sort direction is descending. This explains why clicking on the header produces the correct sort. It seems like changes in the Appli builder were saved to the cloud, including changing the sort direction to ascending, and your device is running an older version of your app locally. Clicking of the multi-color circle on the right of the screen will open a menu. From this menu you can click "Refresh" to pull any changes from the cloud. This should give you the correct sort. When an app is added to the Appli player, the latest version is downloaded from the cloud. This is why the sort order is correct on my end. Subsequent runs of the app will load using local data. We plan to add a way for developers to specify if an app should load from local or cloud.
Let me know if refreshing your app produced the correct sort order.
Posts: 24
Threads: 17
Joined: Jun 2022
Reputation:
0
Yes, refreshing the app produced the correct sort order; thank you.
Of course, I'm going to add something about this to my list of feature requests for the Appli Player :-)
Thanks again, Alex.