PIM import overwrites part fields that are not specified in the XSL file

Summary:

In our implementation of the Import Parts integration to import parts from PIM to CPQ, we are using the default Result Parser XSL file to map the PIM fields to the CPQ fields.

During this integration, the fields that are not specified in the Result Parser are rendered null. So any information that is added to the parts manually is overwritten every time the integration is run (provided the item is imported from PIM). We require that any custom fields that are added manually not be modified, specifically because we need this info on the parts (eligibility rules would not work otherwise).