OData Project Schema TaskStatusManagerUID Not Synchronized

%3CLINGO-SUB%20id%3D%22lingo-sub-1364364%22%20slang%3D%22fr-FR%22%3EOData%20Project%20Schema%20TaskStatusManagerUID%20Not%20Synchronized%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364364%22%20slang%3D%22fr-FR%22%3E%3CP%3EThe%20TaskStatusManagerUID%20is%20not%20properly%20propagated%20into%20the%20OData%20flow%2C%3C%2FP%3E%3CP%3Eand%20updating%20this%20field%20using%20Project%20Pro%20client%20will%20result%20into%20the%20original%20TaskStatusManagerUID%20to%20be%20still%20returned%20using%20the%20OData.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1364364%22%20slang%3D%22fr-FR%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOnline%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EProject%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EProject%20Desktop%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EProject%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EReporting%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

The TaskStatusManagerUID is not properly propagated into the OData flux,

and updating this field using Project Pro client will result into the original TaskStatusManagerUID to be still returned using the OData.

 

 

 

1 Reply

Hello @pascalito,

 

I am actually facing the same issue where the TaskStatusManagerUID in the plan is not reflecting the same from the oData feeds.

 

Have you figured it out?

 

Thanks,

GhisC