![]() ![]() ![]() ![]() if you delete task 3 in project and create a new task, say "5" the ID & unique ID's would be as follows 1,2,3,4 & 1,2,3,5 respectively. Lets say you create tasks 1,2,3,4 and they have an ID of 1,2,3,4 and Unique ID of 1,2,3,4. Unique ID may be important if you are tracking activities by their originally created ID that does not change in MS Project for example. For example, a task's unique ID is the same as the task ID in Windchill, so if you delete or reorder activities in Windchill and then export to project, it takes the current PJL ID and makes that the unique ID. One of the things I found though is that the PJL XML isn't 100% compliant with the MS Project schema. Maybe see what neutral format PlanView uses for data transfer? If it is compliant with the MS Project schema, then try exporting out as XML and see how it loads into ProjectLink. The mechanism for transferring data between MS Project and Windchill is xml using MS Project's XML schema. We have not used PlanView but are working a project to integrate Windchill with MS Project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |