Cursor needs to be updated to accept systemModifiedAt fields that are greater than or equal to "0001-01-01T00:00:00Z"

[igor-ctrl]

Title

Business Central Connector: Need support for legacy records with minimum datetime systemModifiedAt values

Description

We're encountering an issue with the Business Central connector related to legacy records in our tenant that were created before the introduction of the systemModifiedAt field in the API pages.

Current Behavior

• Some records in our Business Central tenant (initialized in 2016/2017) have systemModifiedAt values of 0001-01-01T00:00:00Z
• These records were created before the systemModifiedAt field was introduced and never had subsequent triggers to update this field
• The connector's cursor appears to be filtering out these records, preventing them from being synced

Expected Behavior

• The connector should accept and process records with systemModifiedAt values greater than or equal to 0001-01-01T00:00:00Z
• This would ensure complete data synchronization, including legacy records

Impact

• Missing legacy records in our data warehouse
• Incomplete historical data for business analysis
• Potential data inconsistency issues
• Continued ticket requests from Fivetran

Technical Details

• Tenant initialization date: 2016/2017
• Affected records: Those created before systemModifiedAt field implementation
• Current minimum datetime value affected: 0001-01-01T00:00:00Z

Proposed Solution

Modify the connector's cursor logic to:

1. Accept records with systemModifiedAt values greater than or equal to 0001-01-01T00:00:00Z
2. Consider these as valid timestamps for the initial sync
3. Include these records in the regular incremental sync process

Additional Context

This issue specifically affects Business Central tenants that were initialized before the introduction of the systemModifiedAt field in the API pages. While the connector works excellently for newer records, this adjustment would ensure comprehensive data coverage for long-standing Business Central implementations.

Environment

• Connector: Business Central
• Tenant Creation Date: 2016/2017
• API Version: v2.0

Would you please review this request and advise on the feasibility of implementing this cursor adjustment? This would greatly help ensure complete data synchronization for the Microsoft Dynamics 365 Business Central implementations.

---

Thank you for your attention to this matter. Please let me know if you need any additional information or clarification.