Skip to main content
Planview Customer Success Center

AdditionalID is not modified when using SaveUDF() method in API

SYMPTOMS:
1- Create an engagement with billing office BO1
2- Insert a value for UDF1 for the engagement
3- Change the billing office of the engagement to BO2
4- Insert a value for UDF2 for the engagement

All UDFs are under the same engagement however only UDF2 is visible in the UI.

REASON:
UDF1 has BO1 in AdditionalID column, and UDF2 has BO2 which is the same as the current billing office of the engagement, hence only BO2 is visible in UI.


RESOLUTION:
Change the way API is used by the custom code, as follows:

1- Create an engagement with billing office BO1
2- Insert a value for UDF1 for the engagement
3- If the billing office of the engagement needs to be modified to BO2, then :
3.1- Remove all UDF values
3.2- Change the billing office of the engagement to BO2
4- Insert both UDF1 and UDF2 for the engagement

Both of the UDFs should have BO2 in the AdditionalID column and all UDFs will be visible in UI.

ADDITIONAL NOTES:
How to delete an existing UDF:

When saving the UDF via SaveUDF() method, do not to provide a value. Prepare the XML as if the UDF is going to be updated but do not put anything (e.g. do not put NULL or any other text) in between the double quotes for the "Value" tag.

When no value is provided for the "value" tag in the XML, API should delete the UDF value from the database.