By default, OmniPlan’s XML file format only includes the minimal amount of information it needs to recreate a schedule: so it doesn’t archive derived values such as the start date, it archives the inputs it uses to calculate the start date.
In general, we suggest that people use Publish & Subscribe actions to integrate with other systems: you can add actions which happen automatically every time someone publishes edits to their document. Those actions can automatically export the document to a variety of file formats (including CSV files or an HTML full report), or even run your own custom AppleScript logic to get things into whatever format you need.
But that said, OmniPlan does have a setting which you can use to archive derived results in its saved XML rather than just its input data. The default is named
WriteExtendedXML, and you can turn it on and off by opening these URLs:
Alternatively, you can turn the setting on and off by running these commands in a Terminal window:
defaults write com.omnigroup.OmniPlan3 WriteExtendedXML -bool true
defaults remove com.omnigroup.OmniPlan3 WriteExtendedXML
(If you’re using the Mac App Store build, you’d use
com.omnigroup.OmniPlan3.MacAppStore in those two commands instead of
Because this archives more information than the usual XML format, you’ll end up with larger file sizes, and it will take longer to save and load your document.
Again, our recommended approach would be to use a Publish action to accomplish whatever it is you’re trying to accomplish instead of reading OmniPlan’s XML directly. But when you need it, this option can come in handy.