Do note that FileMaker considers Sunday to be the first day of the week. Unlike the calendar we designed previously, our calendar is going to be based on the week starting on Monday. Users typically expect to view calendars in a grid or chart format, so that's what we'll do. The relationship graph required for the filtered portal technique However, in this case, we'll be using global variables as our filter criteria so that dramatically decreases the amount of structure needed to create the calendar view. There are performance issues to be aware of when applying portal filters, particularly when using related record data as part of filter calculations. Luckily with FileMaker 18, and as early as FileMaker 11, we can use filtered portals to create calendars.
This approach can make managing edits or updates cumbersome for developers because of the volume of records. Also, you’d have to create 42 fields to store the calendar days that would then be used to set up the relationships between the calendar and event tables. Why 42? There are seven days in a week and we need six rows to cover the number of potential weeks in a month, 7 * 6 = 42.
One option would be to create 42 separate relationships and portals to represent events for each calendar day. Of course, there are several different ways that we can structure a calendar.
I'm going to piggyback on our previously published post, but for this calendar, we're going to specify Monday as the start of the week as opposed to Sunday. Nonetheless, it's a common requirement, so I’ll walk you through the process step by step. I admit, designing a calendar in FileMaker is an involved process.
0 kommentar(er)
