It displays fine, and the columns show the correct dependencies. However, when my client moves a task to the right, an error message is shown to say that the action will cause a scheduling conflict, whereas, based on the settings, dependent tasks should move to the right - as they do in the Omniplan file.Ī couple of hours investigation has shown that none of the tasks exported from Omniplan behave properly in MS Project - changing constraint type has no effect, and they do not move around via dependencies. The Omni Automation support in OmniPlan provides mechanisms for automating the creation and manipulation of projects and their elements, and for integrating external data into the project. Network View Task data is now displayed in a tooltip when the cursor is hovered over a variable in a.
Omniplan depency type full#
Network View Full tasks names are now displayed in the Network View. This release also includes numerous bug and stability fixes. I have compared all the settings for a new task entered in Project, that behaves normally, with ones imported from OmniPlan and can see no differences. OmniPlan 3.12 introduces support for viewing full task names in the Network View. In the following example project concept, the script in the example OmniPlan action plug-in, alters an open project to become a. To rule out a problem with my file, I created a new one with only three dependent tasks exactly the same problems occurred. I have also tested on two different Macs (Omniplan) and PCs (MS Project), and tried both the Project XML and MPX export options. I detest Project as much as everyone else, and love Omniplan, but my client uses it and insists on receiving files in Project. The Omniplan, XML and MS Project files are attached for the three task test in case that is helpful.
You really ought to contact the OmniPlan support ninjas via Help->Send Feedback (which will allow you to attach a copy of your project file with the sensitive information obscured). A dependency line is drawn from the beginning or end of one task (or group, or milestone) to the beginning or end of another. Here are descriptions of the FileWrapper. Type r/o) A FileWrapper that represents a symbolic link to another location. Type r/o) A FileWrapper that represents a regular file with data contents. That’s the only way to make sure that someone who knows the ins and outs of the program sees it in a timely fashion. Type r/o) A FileWrapper that represents a directory with zero or more child wrappers. I don’t have any MP experience, nor a copy of it to play with, so I can’t really offer any suggestions. If you have dragged things around on the OmniPlan Gantt chart, that schedules specific start dates for those tasks rather than letting them fall where the constraints would otherwise allow.