![]() ![]() Merlin had a much cleaner view of the project, and this applies to Tasks or Activities, Resources, and Calendar. It did open the MPP file of the same project, and that was a bit quicker than Merlin. Merlin opened the file in about 2 seconds. Version 2.0.3 was unable to open a MS Project MPX file, both using File>Open and dragging the file to OmniPlan. "Also new and notable! We’re getting started on multi-project support." Fortunately, the Omni people addresed this issue in a recent () blog post: I have exported an Omniplan file to MS Project (using the XML option) and imported it into Project 2007.If asking a simple question resulted in frowny faces, no doubt my review will be unpopular among the fanboyz. ![]() 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. 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. 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). 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. I don't have any MP experience, nor a copy of it to play with, so I can't really offer any suggestions. When resource leveling is enabled for a project, OmniPlan automatically schedules project tasks to make sure resources are being used efficiently. 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. After leveling, resources are never scheduled for more than 100 of their available units at any time, and tasks assigned to resources are scheduled in an order optimized for project completion. If you select all the tasks in your project and click the Reset button in the Task Information inspector to set them all to be scheduled as early as constraints allow, then export to MP, does the resulting document work properly (ignoring any issues about how some things aren't starting at the right time because you didn't have fixed dates for them in OP)? Not proposing this as a solution, just a way to get a start on isolating the problem, of course. ![]()
0 Comments
Leave a Reply. |