Okay, but that's not interactive; IOW, you can display the attendance, but not toggle individual cells (unless you really invest into this).
Yes, but sometimes the investment is worth it. In this demo, it is quite easy to replicate and put into place. Also (smile), filtered portals have been vastly improved (please see below)
Hey Joe, we can use filtered portals and it can probably be optimised further. This was my quick first stab ... and you can make ticks and Xs but this is quick so please excuse the kludge. There is a grouped portal and field - I made it grey so it is easy to see. This is how to replicate:
- Copy the grey portal and field inside and paste onto the next day.
- Select it, right-click and select Portal setup. Change the filter calc to the next repetition number.
- Select it, right-click and select script trigger and set the script parameter to the next repetition number
- Select it, right-click and select conditional formatting and change to the next repetition number.
You can also change that repetition calculation to exclude weekends but I'm no Repetition Master so it would take me more time than I have to adjust the calc. Comment would surely know since these types of techniques were originally taught to me by him anyway.
---- further information on portal filtering ----
BTW, filtered portals had been improved in 12 to where it would perform the task on server at times (here is cut and paste - it was from TechNet for those that are registered https://fmdev.filema...e/123083#123083:
What I heard from I-don't-remember-which-FMI-employee during I-don't-remember-which-webinar is that the server only takes over the calculation in certain very simple filter calculations that 1) only reference fields in the table occurrence being filtered (i.e. the TO of the portal), and 2) only compare those fields to constant values. (So comparing BaseTable::field > PortalTable::field would not get the optimized treatment.) There was some uncertainty as to whether the server-side optimization would work if the comparison referenced $$variables (and some embarassing ignorance from the FMI rep who wasn't sure if it was valid to use $$variables in a portal filter calculation!). I could be misremembering some significant details.
just spoke with Matt O'Dell, and he confirmed what "jbante" posted. That is, the only change in Portal Filter Optimization between FileMaker Server 11 and FileMaker Server 12 is when comparing a field in the referenced portal to a constant value, as this is executed at the Server before sending the results to the client. All other occurrences, including referencing global variables, are performed on the client side.
But 13 has further optimised portal filtering. This was copy/pasted into my FM bible so it came from either Comment, Ray Cologon, or an FMI engineer. I haven't had time to find it again to provide the exact reference.
Portals now are treated like relational as long as the value you are referencing does not have to be downloaded to client to determine such as sort.
I am not sure whether the global date will make a difference in this case. It is possible that, since this is for data-entry, you can use an unstored calculation instead of gDate as Get ( CurrentDate ) and remove the global from the filtering completely. Prior to 12, portal filtering ... oh dear, I just realised you ARE on version 11. Well, if you can keep the related record set smaller (under 1,000 or so), it should be fine too. It would not be difficult to constrain this relationship to only current attendance.
And now this has taken way more time than I had, my apology. But I hope it is helpful to provide other options. I've used this for attendance selection in the past and I know it works. We might even be able to use GetLayoutObjectAttribute() so only one naming takes place instead of three.
Small bug - demo removed - I'll repost it within 2 hours. I forgot we need to use triggers instead of buttons.
Demo replaced. I changed the buttons to script triggers. This is because the script evaluation must take place from the context of the filtered portal instead of the parent record.
Edited by LaRetta, 21 July 2014 - 12:46 PM.