Introducing: Dynamics 365 Field Service Integration with Business Central (2024 release wave 1)

Overview

The session introduces the integration between Dynamics 365 Field Service and Business Central. It covers the value of the integration, enabling it through an assisted setup guide, and the prerequisites: a Dataverse connection with Sales and Field Service installed, and existing resource-product couplings uncoupled.

The demos follow the data flow. Resources sync to bookable resources, project tasks link work orders to Business Central projects, and items sync for use in work order product and service lines. Consumption marked as used in Field Service goes to project journals in Business Central. From the resulting project planning lines, a sales invoice is created, and the posted invoice goes back to Field Service.

Key points

• Prerequisite: a Dataverse connection with Sales and Field Service installed; the assisted setup guide covers enabling the integration, project journal template and batch, hours unit of measure and sync settings.
• Resources sync to bookable resources, replacing the earlier product-based sync. Resources need base unit of measure hours, must not be blocked and must not use timesheets. Existing resource-product couplings may need to be uncoupled.
• Only project tasks of type posting are synchronized. Work orders can be created from a project task, and the standard coupling actions are available on the project task card.
• Items must have the field service product type set manually to be usable in Field Service. This is not automatic, for performance and resource reasons.
• Inventory and non-inventory items sync as work order products, and service-type items sync as work order services. Quantity on hand is shown for the selected product.
• Work order sync needs project journal templates and batches designated, and Field Service invoice creation disabled.
• Setting work order products and services to used sends consumption to the project journal. Project planning lines can become a sales invoice, and a recurring job transfers posted invoices back to Field Service asynchronously.

Features

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• other “field service settings” at 5:41
• table “bookable resource” at 8:12
• table “customer assets” at 8:33
• table “project task” at 8:33
• other “work order” at 0:56
• table “project journal” at 4:19
• other “Bookable Resource” at 16:48
• other “Project Task” at 13:42
• other “Work Order Product” at 16:32
• other “Work Order Service” at 17:08
• other “Project Journal Template” at 21:09
• other “Project Journal Batch” at 21:09
• other “Project Planning Lines” at 22:43
• other “Sales Invoice” at 24:25

Not found in BC28-30: table “bookable resource”, table “customer assets”, table “project task”, table “project journal”.

Quotes

• 9:55 “in order to use the products from business Central in field service we will need to make sure that the products have the field”
• 13:02 “you have the standard set of uh actions that you are that users are used to from our uh Dynamics 365 or sales integration”
• 14:19 “we could just go ahead and uh create a new work order you can see the data from business Central has uh already been”
• 16:32 “in business Central we are uh synchronizing uh uh items of type inventory and uh non-inventory items and they can be picked in workorder”
• 16:48 “you can also uh you will also be able to see a quantity on hand for the selected uh for the selected uh product”
• 20:49 “once we uh once we set the the workorder product uh uh line uh workorder products and workorder services as in a state used”
• 23:45 “once you get the once you get the project planning lines you can simply create uh an invoice and uh that invoice that gets”

Presenters (as heard): Ivan ktic, Andre.