When importing tasks from Microsoft Project it comes with a blank external ID.
The problem is that without an external ID I am not able to update the task in a programatically way, i.e., through a XOG.
If I try to XOG IN the task without an external ID, the XOG will duplicate the task, even if I use the "internalTaskID".
For example, if I simply XOG OUT the project with its tasks and then XOG IN IT again (without any change) all tasks will be DUPLICATED.
Does anyone know how to solve this ?
Thanks in advance.
Hi Vitor. Sadly, there is no solution for this - for Task XOG to work, the ID must be present.
The way I have resolved this is two-fold:
(1) run a process periodically which updates the Task ID to match the Internal ID (using a completely unsupported SQL update)
(1b) set up auto-numbering on Task ID so the problem doesn't happen in future (but that only works for tasks created in PPM, not tasks created in MSP)
(2) place some VBA into the MS Project interface which checks to ensure every task has a Task ID.
You could maybe get around the unsupported SQL update by making Task ID a mandatory field, but I don't know what affect the MSP interface will have.
This is a long-standing frustration (see Update Task information with blank task id(PREXTERNALID) , Xog to create new task in WBS STRUCTURE , Task update through GEL/XOG... , How to have task ID assigned to tasks that are imported from MS Project , Update task Name by XOG )
Thanks for your answer, although It confirms my frustration.
It seems that option "1-SQL update of the Task ID" is the eficientest option, although it could be risky.
I will also contact CA Support to ask permission for the SQL update.