Separation Model
DayBackOnline.SeparationModel History
Hide minor edits - Show changes to output
Changed lines 1-11 from:
!! Do I need to do anything different when pasting the calendar into a separated system?
Not really. Of our two integration methods, if you're [[QuickIntegration | linking]] the calendar (instead of pasting it into your file), separation isn't an issue at all. The calendars events table (along with contacts and projects) will be in your data file but the other tables can stay in our calendar file.
If you're [[embedding the calendar]] into your file, then the graph shown in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
The SampleEvents table there can be in another file (your data file, presumably).
'''Color Coding in Separated Files.'''
If you want to show an event's color "on"the event record in list view and in the Event Details mini window, follow these [[SeparationColors | instructions]].
The SampleEvents table there can be in another file (your data file, presumably).
'''Color Coding
If you want to show an event's color "on"
to:
!! Do I need to do anything different when using DayBack Online with a separated system?
No. The admin settings page in DayBack Online (where you configure your FileMaker calendar sources) asks for a File name and a Layout name. In a separated system these can be either in the interface file or in the data file, but they need to be from the same file.
There is one other consideration around access. You'll need to grant XML web publishing privileges to your data file in any case: if you use a layout in you interface file you'll need to grant XML web publishing privileges to both the interface file and the data file. And the FileMaker account name and password you put in the [[PHPrelay file]] will also need to work in the data file for sure, but in both the data file and the interface file if you use a layout from interface.
If you have more questions about this, please don't hesitate to %newwin% [[https://www.seedcode.com/contact/ | contact us]].
No. The admin settings page in DayBack Online (where you configure your FileMaker calendar sources) asks for a File name and a Layout name. In a separated system these can be either in the interface file or in the data file, but they need to be from the same file.
There is one other consideration around access. You'll need to grant XML web publishing privileges to your data file in any case: if you use a layout in you interface file you'll need to grant XML web publishing privileges to both the interface file and the data file. And the FileMaker account name and password you put in the [[PHPrelay file]] will also need to work in the data file for sure, but in both the data file and the interface file if you use a layout from interface.
If you have more questions about this, please don't hesitate to %newwin% [[https://www.seedcode.com/contact/ | contact us]].
Deleted lines 11-35:
You can leave the CalendarColors table in your Calendar UI file, but since there is actual data in that table, you might rather have it in your data file. If you do that, you'll have to make a few changes:
-> 1. Create an unstored calculation field called "z_RecordNumberCalc" in the CalendarColors table in your data file. The formula should be simply: Get(RecordNumber)
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_1.jpg]]
-> 2. Create a new TO in the Calendar interface file, associated with the CalendarRows table, and name it "CalendarColorRows". Relate it to CalendarColors TO as z_RecordNumberCalc = RowNumber.
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_2.jpg]]
-> 3. Create a new field in the CalendarRows table in your Calendar interface file called DragTarget_nonCalendar. You can copy/paste the formula from the ColorDragTarget calc field formula in the original CalendarColors table.
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_3.jpg]]
-> 4. On the Assign Colors layout in the Calendar UI file, select the field object currently mapped to the CalendarColors::ColorDragTarget field. Make sure you have the right object; there are two fields layered on top of each other there.
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_4.jpg]]
->Remap that field object to CalendarColorRows::DragTarget_nonCalendar.
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
-> That's it.
Changed lines 17-18 from:
Attach:FBz_22899_1.jpg
to:
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_1.jpg]]
Changed lines 21-22 from:
Attach:FBz_22899_2.jpg
to:
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_2.jpg]]
Changed lines 25-26 from:
Attach:FBz_22899_3.jpg
to:
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_3.jpg]]
Changed lines 29-30 from:
Attach:FBz_22899_4.jpg
to:
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_4.jpg]]
Changed line 34 from:
%center% %width=200px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
to:
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
Changed line 33 from:
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
to:
%center% %width=200px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
Changed line 33 from:
%center% %width=500px %newwin [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
to:
%center% %width=500px newwin% [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
Changed line 33 from:
Attach:FBz_22899_5.jpg
to:
%center% %width=500px %newwin [[Attach:FBz_22899_5.jpg | Attach:FBz_22899_5.jpg]]
Deleted lines 35-36:
%center% %width=400px newwin% [[Attach:test.png | Attach:test.png]]
Changed line 37 from:
%center% %width=200px newwin% [[Attach:test.png | Attach:test.png]]
to:
%center% %width=400px newwin% [[Attach:test.png | Attach:test.png]]
Changed line 37 from:
%width=500px newwin% [[Attach:test.png | Attach:test.png]]
to:
%center% %width=200px newwin% [[Attach:test.png | Attach:test.png]]
Changed lines 35-39 from:
-> That's it.
to:
-> That's it.
Attach:test.png
%width=500px newwin% [[Attach:test.png | Attach:test.png]]
Attach:test.png
%width=500px newwin% [[Attach:test.png | Attach:test.png]]
Changed line 17 from:
to:
Attach:FBz_22899_1.jpg
Changed line 17 from:
Attach:FBz_22899_1.jpg
to:
%width=500 newwin% [[Attach:FBz_22899_1.jpg | Attach:FBz_22899_1.jpg]]
Added lines 9-10:
'''Color Coding in Separated Files.'''
Changed lines 15-16 from:
1. Create an unstored calculation field called "z_RecordNumberCalc" in the CalendarColors table in your data file. The formula should be simply: Get(RecordNumber)
to:
-> 1. Create an unstored calculation field called "z_RecordNumberCalc" in the CalendarColors table in your data file. The formula should be simply: Get(RecordNumber)
Changed lines 19-20 from:
2. Create a new TO in the Calendar interface file, associated with the CalendarRows table, and name it "CalendarColorRows". Relate it to CalendarColors TO as z_RecordNumberCalc = RowNumber.
to:
-> 2. Create a new TO in the Calendar interface file, associated with the CalendarRows table, and name it "CalendarColorRows". Relate it to CalendarColors TO as z_RecordNumberCalc = RowNumber.
Changed lines 23-24 from:
3. Create a new field in the CalendarRows table in your Calendar interface file called DragTarget_nonCalendar. You can copy/paste the formula from the ColorDragTarget calc field formula in the original CalendarColors table.
to:
-> 3. Create a new field in the CalendarRows table in your Calendar interface file called DragTarget_nonCalendar. You can copy/paste the formula from the ColorDragTarget calc field formula in the original CalendarColors table.
Changed lines 27-28 from:
4. On the Assign Colors layout in the Calendar UI file, select the field object currently mapped to the CalendarColors::ColorDragTarget field. Make sure you have the right object; there are two fields layered on top of each other there.
to:
-> 4. On the Assign Colors layout in the Calendar UI file, select the field object currently mapped to the CalendarColors::ColorDragTarget field. Make sure you have the right object; there are two fields layered on top of each other there.
Changed lines 31-33 from:
Remap that field object to CalendarColorRows::DragTarget_nonCalendar.
Attach:FBz_22899_5.jpg
Attach:FBz_22899_5.
to:
->Remap that field object to CalendarColorRows::DragTarget_nonCalendar.
Attach:FBz_22899_5.jpg
-> That's it.
Attach:FBz_22899_5.jpg
-> That's it.
Added lines 15-16:
Attach:FBz_22899_1.jpg
Added lines 19-20:
Attach:FBz_22899_2.jpg
Changed lines 23-31 from:
to:
Attach:FBz_22899_3.jpg
4. On the Assign Colors layout in the Calendar UI file, select the field object currently mapped to the CalendarColors::ColorDragTarget field. Make sure you have the right object; there are two fields layered on top of each other there.
Attach:FBz_22899_4.jpg
Remap that field object to CalendarColorRows::DragTarget_nonCalendar.
Attach:FBz_22899_5.jpg
4. On the Assign Colors layout in the Calendar UI file, select the field object currently mapped to the CalendarColors::ColorDragTarget field. Make sure you have the right object; there are two fields layered on top of each other there.
Attach:FBz_22899_4.jpg
Remap that field object to CalendarColorRows::DragTarget_nonCalendar.
Attach:FBz_22899_5.jpg
Changed lines 9-19 from:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow these [[SeparationColors | instructions]].
to:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow these [[SeparationColors | instructions]].
You can leave the CalendarColors table in your Calendar UI file, but since there is actual data in that table, you might rather have it in your data file. If you do that, you'll have to make a few changes:
1. Create an unstored calculation field called "z_RecordNumberCalc" in the CalendarColors table in your data file. The formula should be simply: Get(RecordNumber)
2. Create a new TO in the Calendar interface file, associated with the CalendarRows table, and name it "CalendarColorRows". Relate it to CalendarColors TO as z_RecordNumberCalc = RowNumber.
3. Create a new field in the CalendarRows table in your Calendar interface file called DragTarget_nonCalendar. You can copy/paste the formula from the ColorDragTarget calc field formula in the original CalendarColors table.
4. On the Assign Colors layout in the Calendar UI file, select the field object currently mapped to the CalendarColors::ColorDragTarget field. Make sure you have the right object; there are two fields layered on top of each other there. Remap that field object to CalendarColorRows::DragTarget_nonCalendar.
You can leave the CalendarColors table in your Calendar UI file, but since there is actual data in that table, you might rather have it in your data file. If you do that, you'll have to make a few changes:
1. Create an unstored calculation field called "z_RecordNumberCalc" in the CalendarColors table in your data file. The formula should be simply: Get(RecordNumber)
2. Create a new TO in the Calendar interface file, associated with the CalendarRows table, and name it "CalendarColorRows". Relate it to CalendarColors TO as z_RecordNumberCalc = RowNumber.
3. Create a new field in the CalendarRows table in your Calendar interface file called DragTarget_nonCalendar. You can copy/paste the formula from the ColorDragTarget calc field formula in the original CalendarColors table.
4. On the Assign Colors layout in the Calendar UI file, select the field object currently mapped to the CalendarColors::ColorDragTarget field. Make sure you have the right object; there are two fields layered on top of each other there. Remap that field object to CalendarColorRows::DragTarget_nonCalendar.
Changed line 3 from:
Not really. Of our two integration methods, if you're [[QuickIntegration | linking]] the calendar (instead of pasting it into your file), separation isn't an issue at all.
to:
Not really. Of our two integration methods, if you're [[QuickIntegration | linking]] the calendar (instead of pasting it into your file), separation isn't an issue at all. The calendars events table (along with contacts and projects) will be in your data file but the other tables can stay in our calendar file.
Changed line 5 from:
If you're pasting the calendar into your file, then the graph shown in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
to:
If you're [[embedding the calendar]] into your file, then the graph shown in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
Changed lines 3-5 from:
Not really-- the graph shown in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
to:
Not really. Of our two integration methods, if you're [[QuickIntegration | linking]] the calendar (instead of pasting it into your file), separation isn't an issue at all.
If you're pasting the calendar into your file, then the graph shown in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
If you're pasting the calendar into your file, then the graph shown in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
Changed line 7 from:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow step 6 in these [[QuickIntegration | instructions]].
to:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow these [[SeparationColors | instructions]].
Changed line 7 from:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow these [[QuickIntegration | instructions]].
to:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow step 6 in these [[QuickIntegration | instructions]].
Changed lines 7-26 from:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, you'll need a table occurrence for the "CalendarRows" table in your data file (it doesn't need to be related to any other T.O.), and you'll need to add the "z_sc_ColorCalc" field from our SampleEvents table into the Events table in your data file (just copy/paste it if you have FileMaker Advanced).
The "z_sc_ColorCalc" field looks for global variables that are now scoped to your interface file, so you need to create these variables in your data file as well. Here's how:
Create a Cartesian (the "x" operator) relationship in your data file to the "CalendarColors" table from any other table (your "Events" T.O. perhaps?). Then make a new layout called "Assign Colors", based on that same T.O. (e.g., "Events"), and copy/paste the Calendar Colors portal from the "Assign Colors" layout in the interface file.
Then create a new script in your data file called "Apply Color Settings in Data File" by copy/pasting only the steps shown below from the Calendar file's "Apply Color Settings { Close ; DontRefresh }" script.
-> # \\
Go to Layout ["Assign Colors" (Events)] \\
# \\
Loop \\
Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ] \\
Go to Portal Row [Select; Next; Exit after last] \\
End Loop \\
# \\
Go to Layout [original layout] \\
# \\
Make sure this script runs when your data file opens (note that if this script is set up to be triggered by "OnFirstWindowOpen" and your data file never actually opens in a window, these color settings won't be propagated).
The "z_sc_ColorCalc" field looks for global variables that are now scoped to your interface file, so you need to create these variables in your data file as well. Here's how:
Create a Cartesian (the "x" operator) relationship in your data file to the "CalendarColors" table from any other table (your "Events" T.O. perhaps?). Then make a new layout called "Assign Colors", based on that same T.O. (e.g., "Events"), and copy/paste the Calendar Colors portal from the "Assign Colors" layout in the interface file.
Then create a new script in your data file called "Apply Color Settings in Data File" by copy/pasting only the steps shown below from the Calendar file's "Apply Color Settings { Close ; DontRefresh }" script.
-> # \\
Go to Layout ["Assign Colors" (Events)] \\
# \\
Loop \\
Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ] \\
Go to Portal Row [Select; Next; Exit after last] \\
End Loop \\
# \\
Go to Layout [original layout] \\
# \\
Make sure this script runs when your data file opens (note that if this script is set up to be triggered by "OnFirstWindowOpen" and your data file never actually opens in a window, these color settings won't be propagated)
to:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow these [[QuickIntegration | instructions]].
Changed lines 15-25 from:
#
Go to Layout ["Assign Colors" (Events)]
#
Loop
Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ]
End Loop
#
Go to Layout [original layout]
Go to Layout ["Assign Colors" (Events)]
Loop
Go to Layout [original
to:
--> #
Go to Layout ["Assign Colors" (Events)] \\
# \\
Loop \\
Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ] \\
Go to Portal Row [Select; Next; Exit after last] \\
End Loop \\
# \\
Go to Layout [original layout] \\
# \\
Go to Layout ["Assign Colors" (Events)] \\
# \\
Loop \\
Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ] \\
Go to Portal Row [Select; Next; Exit after last] \\
End Loop \\
# \\
Go to Layout [original layout] \\
# \\
April 16, 2013, at 12:17 AM
by - How to make the color appear "on" the event record with separation model
Changed lines 7-11 from:
That calc also looks for global color variables that are now scoped to your interface file, so you'll want
To do this take a look at the script "Apply Color Settings { Close ; DontRefresh }" and you'll see we loop through the CalendarColors records to cast them as global variables. You somehow need to cast those same variables in your data file as well
to:
If you want to show an event's color "on" the event record in list view and in the Event Details mini window, you'll need a table occurrence for the "CalendarRows" table in your data file (it doesn't need to be related to any other T.O.), and you'll need to add the "z_sc_ColorCalc" field from our SampleEvents table into the Events table in your data file (just copy/paste it if you have FileMaker Advanced).
The "z_sc_ColorCalc" field looks for global variables that are now scoped to your interface file, so you need to create these variables in your data file as well. Here's how:
Create a Cartesian (the "x" operator) relationship in your data file to the "CalendarColors" table from any other table (your "Events" T.O. perhaps?). Then make a new layout called "Assign Colors", based on that same T.O. (e.g., "Events"), and copy/paste the Calendar Colors portal from the "Assign Colors" layout in the interface file.
Then create a new script in your data file called "Apply Color Settings in Data File" by copy/pasting only the steps shown below from the Calendar file's "Apply Color Settings { Close ; DontRefresh }" script.
#
Go to Layout ["Assign Colors" (Events)]
#
Loop
Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ]
Go to Portal Row [Select; Next; Exit after last]
End Loop
#
Go to Layout [original layout]
#
Make sure this script runs when your data file opens (note that if this script is set up to be triggered by "OnFirstWindowOpen" and your data file never actually opens in a window, these color settings won't be propagated).
The "z_sc_ColorCalc" field looks for global variables that are now scoped to your interface file, so you need to create these variables in your data file as well. Here's how:
Create a Cartesian (the "x" operator) relationship in your data file to the "CalendarColors" table from any other table (your "Events" T.O. perhaps?). Then make a new layout called "Assign Colors", based on that same T.O. (e.g., "Events"), and copy/paste the Calendar Colors portal from the "Assign Colors" layout in the interface file.
Then create a new script in your data file called "Apply Color Settings in Data File" by copy/pasting only the steps shown below from the Calendar file's "Apply Color Settings { Close ; DontRefresh }" script.
#
Go to Layout ["Assign Colors" (Events)]
#
Loop
Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ]
Go to Portal Row [Select; Next; Exit after last]
End Loop
#
Go to Layout [original layout]
#
Make sure this script runs when your data file opens (note that if this script is set up to be triggered by "OnFirstWindowOpen" and your data file never actually opens in a window, these color settings won't be propagated).
Changed lines 3-4 from:
Not really-- the graph show in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
to:
Not really-- the graph shown in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
Changed lines 9-11 from:
That's it.
to:
That calc also looks for global color variables that are now scoped to your interface file, so you'll want to create these color variables in your data file as well.
To do this take a look at the script "Apply Color Settings { Close ; DontRefresh }" and you'll see we loop through the CalendarColors records to cast them as global variables. You somehow need to cast those same variables in your data file as well. One way is to add a portal to CalendarColors somewhere in your data file and bring in a version of this script to loop through them. You'll want to do this on start up.
To do this take a look at the script "Apply Color Settings { Close ; DontRefresh }" and you'll see we loop through the CalendarColors records to cast them as global variables. You somehow need to cast those same variables in your data file as well. One way is to add a portal to CalendarColors somewhere in your data file and bring in a version of this script to loop through them. You'll want to do this on start up.
Added lines 1-9:
!! Do I need to do anything different when pasting the calendar into a separated system?
Not really-- the graph show in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
The SampleEvents table there can be in another file (your data file, presumably).
There is one calc in SampleEvents that needs to know about the CalendarRows table: the optional calc you may want to use if you wish to show events colors "on" the event record in list view or in the Event Details mini window. So you'll want to add a table occurrence for CalendarRows to your data table so the calc "z_sc_ColorCalc" can evaluate properly.
That's it.
Not really-- the graph show in our [[integration]] article should be in your Interface file just as it is shown in that article. All the layouts mentioned there should be in your interface file as well.
The SampleEvents table there can be in another file (your data file, presumably).
There is one calc in SampleEvents that needs to know about the CalendarRows table: the optional calc you may want to use if you wish to show events colors "on" the event record in list view or in the Event Details mini window. So you'll want to add a table occurrence for CalendarRows to your data table so the calc "z_sc_ColorCalc" can evaluate properly.
That's it.
