Skip to content

Need new Event to manage the Resource Sync in case of FS to BC integration for Service Order #29807

@Merc-Sagar

Description

@Merc-Sagar

Why do you need this change?

Hello,

With reference to the case registered with Microsoft with Tracking ID 2602100030007972, the consultant has suggested to create a new request for new event in BC. The details of the case are as below

SYMPTOM: The customer is experiencing an issue where the Resource in Service Order records are not syncing from Dynamics 365 CRM to Business Central as expected. The Field Service Status in Business Central is incorrectly received as Cancelled instead of Completed, causing synchronization failure.

CAUSE: The root cause is that the customer has two 'Completed' statuses in the FS Booking Status table in CRM. However, Business Central fetches only the first 'Completed' status record, which corresponds to 'Closed - Awaiting paperwork', leading to a mismatch. This mismatch causes Business Central to receive a Cancelled status instead of the correct Completed status, preventing resource synchronization.

RESOLUTION: Our development team confirmed that Business Central doesn't have an event for the 'Booking Status Name', and you would need to submit a request for a new 'Publisher' creation. The request can be submitted through this 'GitHub Repository' Issues · microsoft/ALAppExtensions, through these steps (Issues > New Issue > Create Extensibility Request).

Describe the request

Attaching the changes needed here.

  1. in Codeunit 6616 "FS Integration Mgt." - Should provide the event to update or add own filter. We must be able to overwrite the default filter.
Image
  1. in Codeunit 6610 "FS Int. Table Subscriber" - This is the calling function. If the above is not feasible, a filter update to be available here.
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    missing-infoThe issue misses information that prevents it from completion.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions