Hi mertadsay,
You're asking why project tasks from newly created projects aren’t syncing to Dataverse, even though tasks from system projects and their sub-tasks sync correctly. You’ve confirmed there are no errors or skipped records in the integration log, which suggests the sync job is running—but silently ignoring those new records.
Here’s what might be happening and how to resolve it:
1. Check Coupling Status
Dataverse sync jobs typically only process coupled records. If your new projects are not manually coupled to Dataverse records, their related tasks may be skipped.
- Go to the Integration Table Mapping page
- Select the
PROJECT mapping and open the Coupling action
- Confirm that your new projects are coupled to Dataverse records
- If not, manually couple them or enable auto-coupling in the sync setup
2. Review Field Mapping for Project Tasks
The sync engine uses Integration Field Mapping to determine which fields to transfer. If your custom or newly added fields aren’t mapped correctly, the sync may ignore them.
- Open the Integration Field Mapping page for
PROJECT TASK
- Confirm that required fields like
Project No. and Task ID are mapped
- If you’ve added custom fields, ensure they’re included in the mapping
3. Validate Sync Job Filters
Some sync jobs apply filters based on status, ownership, or timestamps.
- Check the Job Queue Entry for the sync job
- Review any filters or conditions that might exclude new project tasks
- Try running the job manually to see if the tasks are picked up
4. Consider Custom Sync Logic (if needed)
If the standard sync doesn’t meet your needs, you can extend the sync behavior using events in Codeunit Integration Rec. Synch. Invoke.
Here’s a sample to intercept and include custom logic:
al
[EventSubscriber(ObjectType::Codeunit, Codeunit::"Integration Rec. Synch. Invoke", 'OnBeforeInsertRecord', '', true, true)]
local procedure HandleProjectTaskInsert(SourceRecordRef: RecordRef; var DestinationRecordRef: RecordRef)
begin
// Add logic to ensure new project tasks are included
end;
Here’s a helpful link showing how to configure and troubleshoot Dataverse sync for custom tables and mappings:
Synchronizing Business Central and Dataverse – Microsoft Learn
Add Table and Field Mappings to Existing Integration – Dynamics 365 Lab
Business Central & Dataverse Integration Samples – GitHub
If you find this helpful, feel free to mark this as the suggested or verified answer.
Cheers
Jeffrey
