Views:

Applies to Product - Dynamics 365 Commerce

What’s happening?
  1. When clicking the 'Run project' button for any data project, the system displays the message: 'Object reference not set to an instance of an object.' The project completes successfully despite the error message.
  2. DMF Batch job that loads sales orders is failing, causing issues with the monitor job.

 

Reason:

  1. The error message 'Object reference not set to an instance of an object' is identified as a known bug, which is addressed in an quality update.
  2. The error in the DMF Batch job is due to custom code not being compatible with the new retry design changes in recurring integration.

 

Resolution:

  1. For the data project error, it is advised to take fix via new quality update.
  2. For the DMF Batch job issue, the following steps should be taken:
  3. Identify the custom code that involves SysIntegrationActivityBatch and SysIntegrationActivityBatchTask classes.
  4. Update the custom batch tasks to be added to Job2 instead of Job1, aligning with the new design where Job1 creates a new runtime child job (Job2).
  5. Test the updated custom code to ensure it works correctly with the new design.
  6. If needed, enable the flights DMFDisableRecurringIntegrationImportRetry and DMFDisableRecurringIntegrationImportRetryV2 to temporarily use the older design and unblock processes.