Primavera will take the summary task and create a WBS node so any logic that previously existed will be removed. But that is a topic for another blog post. Whilst being a lazy way of planning a project, summary logic can in fact create a situation where the plan is artificially extended. Planners should never use summary bar logic in the first place because it makes the logic difficult to follow. The problem is that these are not "blank rows" at all, they become treated as errors by Primavera's import engine. Microsoft project allows users to skip lines within the activity grid. Scrutiny of these files will help pin-point the errors and help you to resolve them. During an import several files are generated in the log file directory: However, the import log data can be very confusing. The error log file is key to understanding what goes wrong druing your import. Here's a few hot tips for those of you out there who are constantly experiencing errors when importing: Log Files The process has not been very simple because in the effort to avoid import errors, we have had to firstly correct the MPP file prior to bringing it into Primavera. This week we've been busy importing numerous Microsoft Project files into Primavera P6 to analyse delay claims.
0 kommentar(er)
