A critical issue when importing new costing sheet nodes using the "Costing sheet nodes and absorption basis" entity.

The problem arises when parts of the costing sheet fail during import, whereas importing the full costing sheet results in the deletion of all existing costing sheets, including rates.

Additionally, using the "Costing Sheet Node Calculation Factors V2" entity causes rates to be in a pending state, leading to the deletion of old rates, which disrupts report accuracy.

This issue has been acknowledged by the product team and is noted as "By design" in the official documentation.

Specifically, when importing the cost sheet node entity, the existing cost sheet is entirely deleted before the new costing sheet is saved.

To address this, we propose changing the validation process during entity import to allow partial imports without deleting existing data. This change is crucial for maintaining data integrity and ensuring accurate financial reporting.

Moreover, if new indirect costs or rates need to be imported, the current issue necessitates significant manual work, further complicating the process.

It will be great to reconsider this design and implement a solution that preserves existing costing sheets and rates during the import process.

For more details, refer to the issue highlighted by the product team: https://fix.lcs.dynamics.com/Issue/Details?bugId=606746