I am wondering if you guys have a idea how to resolve this issue with a customer solution.

- Zulu does not like calculated or related fields
- My solution to this was to script the calculation (on record load) of a few fields that are used by zulu to display the calendar title and calendar notes/detail. The calendar notes in particular are fairly complex - using SQL to calc such.
- problem is that the script updates the modification timestamp.
- result is that this creates weird sync conflicts
- if I disable the script that modifies the fields, then sync conflicts naturally go away, however so does updates to fields important to Zulu.

I am wondering if you have any ideas on how to resolve this. Once solution would be to store the fields that zulu requires in a one-to-one related records. But my understanding is that Zulu does not play well with related records.

Hi Darren,

Thanks for your note. Zulu is now being supported by 360Works, our co-authors on this project. I've CC'ed your request to them at [email protected] and you should be hearing back shortly.

All the best,

Jeff