MSP mapping to a Number attribute changes NULL (empty) to 0

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

There is a mapping between a Clarity Number attribute with a Microsoft Project 'NumberX' attribute (e.g.: Number0). After opening the project in MSP and saving back to Clarity, all the values that were NULL (empty) in Clarity for this attribute are now zero (0), even if there were no changes in the project.

Resolution

This is working as per Microsoft Project design - a "NumberX" attribute cannot be null in MSP, so MSP replaces the NULL (empty) value with a 0.

Once the project is saved back to Clarity, we save the information we receive from MSP, which are zeros for every value that was previously NULL.