If I have a single activity (e.g. a trucking move) currently on a single row in the same table with two events (preview date and move date), can I display both in a single calendar? Right now, I'm creating two separate calendars, but worry the user won't see a "preview" appointment.
Solved! Go to Solution.
Hello, I think it's better to keep customer information in one table and events information in a separate table, on the calendar view you can see red marked VisualDate and orange color MoveDate
check out sample i created for you https://www.appsheet.com/templates?appGuidString=4d522957-0d86-4ab9-862f-a05dc85e579b
So with Map views yo have the option to display a "Secondary data table" which can be the same table AFAIK
Simon@1minManager.com
Sorry, for my late follow-up. I'd given up on getting a reply. Also, please forgive my ignorance in that I readily admit to being a newb.
I do see a secondary data table in the Map View; but I'm trying to display a calendar view and can't find a secondary data table in that kind of view. Also, fwiw, all of the data I need is in the same table, just two events in that table for the same client.
So I assume you have two LatLong columns in the table. In the map view you've probably already specified the "For this data" as that table and "Map column" as the first latlong column. Now simply choose the same table in "Secondary data table" and the 2nd latlong column in "Secondary data column"
Currently impossible. I made a feature request years ago, but nothing is happening yet.
https://www.googlecloudcommunity.com/gc/Feature-Ideas/Calendar-view-Additional-Data/idi-p/224621
You may consider changing table's structure like,
The * indicates key columns.
This allows you to show 2 events on same calendar view. To differentiate the events, select "Event" in calendar's Category option.
Thanks for taking the time to reply. My problem is that my data is keyed around the customer. Need to figure out how to distinguish between types of "Event" within the data base and still use time/dates. For now, I've created to calendars. Sample table below:
LastName | VisualDate | MoveDate | |
Smith | jsmith@test.com | 7/15/2022 | 7/17/2022 |
Doe | jdoe@test.com | 7/22/2022 | 8/18/2022 |
Millwood | framkm@test.com | 7/22/2022 | 8/1/2022 |
Gaugan | mgaugan@test.com | 8/1/2022 | |
Faulkner | bfaulkner@test.com | 7/26/2022 | 8/2/2020 |
Sanders | glen@test.com | 08/01/2022 | 8/2/2022 |
Hello, I think it's better to keep customer information in one table and events information in a separate table, on the calendar view you can see red marked VisualDate and orange color MoveDate
check out sample i created for you https://www.appsheet.com/templates?appGuidString=4d522957-0d86-4ab9-862f-a05dc85e579b
You should separate tables, each table has its own key / purpose and then relate them. This's called Normalization in RDBMS world, It's normal good practice for everyone dealing with data.
I also created two separate calendars, one for users and one for me personally. Perhaps for someone it may seem too inconvenient, but I`m into the habit. For myself I use 2023 april calendar, this`s exactly what I print out and hang on the wall. I'm a visual learner, so it's easier for me to memorize. I always have these printouts in the office, it`s simpler to keep track of important meetings and small tasks. Some of my colleagues prefer to use the phone exclusively for this purpose, I guess I'm old-fashioned, but never got used to it=)
User | Count |
---|---|
18 | |
11 | |
7 | |
4 | |
3 |