Separation Model

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 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 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.
That's it.
Follow us: