Business Central: Difference between revisions

Latest revision as of 13:32, 24 October 2024

Integration with third-party systems
Resco CRM Connector (web APIs): REST API service OData service Questionnaire OData service Resco Cloud Client (NuGet) Connect Resco Cloud and Dynamics Business Central Power Automate Resco Cloud connector Resco Reports connector Integrations Glossary entry on integration Woodford configuration Documents (Box, Dropbox, OneDrive, SharePoint) Communication with external applications (via URL schemes) Email integration Exchange (email, calendar, contacts) ~~Google~~ (discontinued) DocuSign integration Marketing services (MailChimp, MailerLite, GetResponse) SMS integration GitHub integration (for Woodford customizations)

Wikipedia has an article on a similar subject:

Microsoft Dynamics 365 Business Central

Microsoft Dynamics 365 Business Central is an enterprise resource planning system from Microsoft. The product is part of the Microsoft Dynamics family.

Different ways exist for Resco technology to interact with your Business Central data.

Resco mobility via Power Platform

Business Central can integrate natively with Dataverse/Power Platform (Microsoft documentation). By installing Resco Suite to your Dataverse/Power Platform environment you can benefit from native integration between Resco and Power Platform and use Resco Mobile CRM as your mobile frontend. Resco fully supports Dataverse's virtual tables, allowing you to access Business Central via Resco mobile apps.

Resco mobility via Microsoft Dynamics

Business Central can integrate natively with Microsoft Dynamics 365 Field Service (Microsoft documentation). By installing Resco Suite to your Dynamics environment you can benefit from native integration between Resco and Dynamics and use Resco Mobile CRM as your mobile frontend. Resco fully supports Dataverse's virtual tables, allowing you to access Business Central via Resco mobile apps.

Integration of Business Central and Dataverse

There are several ways in which Dataverse and Business Central can be integrated. Some of the interaction strategies are discussed in a video by the Microsoft's Business Central team:

To summarize, the available integration options include:

Data Sync that replicates data changes between overlapping tables in Business Central and Dataverse
Virtual tables that enable interaction without data duplication
Data and business events that trigger Power Automate flows

It is important to realize that these different strategies can be combined. Some tables can be duplicated via data sync, other can stay virtual, etc. In addition to the methods listed by the Business Central team, various third-party solutions simplify integration between the two platforms. Ultimately, each project is unique and requires thought and expertise to succeed.

Additional reading:

Integration of Dataverse and Resco

Resco Suite is a solution that you add to your Dataverse. It allows you to set up your mobile experience for Dataverse:

Select which tables, fields, and rows should be available in the Resco Mobile CRM app.
Design the home screen, views, forms, and more.
Add business logic to bind it all together.

Resco Mobile CRM is the mobile app that grants you access to Dataverse data. This includes

Standard Dataverse tables
Dynamics 365 Field Service or Sales tables
Virtual tables of third-party systems such as Business Central or Finance & Operations
Custom tables designed by customer/partner
Custom tables by Resco (needed for extra Resco features such as inspections or timesheets)

Bringing it all together

The out-of-the-box integration between Business Central and Dataverse is gradually improving. Still, many customers prefer to supplement or replace it with a custom solution. What are some things to keep in mind?

Licensing - Make sure that you have all the necessary Microsoft licenses. Many integration scenarios require premium licenses.
Prepare for sync issues - Sooner or later, data will get out of sync. Plan ahead and prepare user-friendly and reliable tools and processes that business users can use even without technical knowledge. On Resco's side, we've got you covered with robust and highly configurable synchronization; detailed logs, Sync Dashboard, etc.
Standard or small - Standard scenarios involving field service or field sales generally work satisfactorily out-of-the-box. If you are working on a custom scenario, consider starting small so that the complexity doesn't overwhelm you.
Competent partner - ERPs are complex systems. Bring in a partner with integration expertise.
Ultimately, each project is different. Select the appropriate integration strategy. Duplicating the data might require re-implementing complex business logic in Dataverse (and possibly Resco Mobile CRM). Virtual tables bring their own set of limitations.

Common scenarios

What are some of the common scenarios involving Resco?

Use Resco's flexible platform to design a custom feature. For example, travel expenses management, with Resco as the mobile client for tracking expenses, scanning receipts, and uploading them to the back office for further processing.
Use some of Resco's popular features, such as digital forms (Resco Inspections) or timesheet management.
Use Resco as the mobile client for Dynamics Sales or Field Service.

@@ Line 1: / Line 1: @@
-{{WIP}}
+{{Integration TOC}} {{Wikipedia|Microsoft Dynamics 365 Business Central}}
-{{Wikipedia|Microsoft Dynamics 365 Business Central}}
 '''Microsoft Dynamics 365 Business Central''' is an enterprise resource planning system from Microsoft. The product is part of the Microsoft Dynamics family.
-== Resco Cloud integration ==
+Different ways exist for Resco technology to interact with your Business Central data.
-[[Resco Cloud]] can connect to Business Central using one of the following methods:
+== Resco mobility via Power Platform ==
-* [[Power Automate]] + Resco Cloud connector - full-featured integration
-* [[Integrations]] (Preview) - for now mostly useful for migration scenarios
+Business Central can integrate natively with '''Dataverse/Power Platform''' ([https://learn.microsoft.com/en-us/dynamics365/business-central/admin-common-data-service Microsoft documentation]). By installing [[Resco Suite]] to your Dataverse/Power Platform environment you can benefit from native integration between Resco and Power Platform and use [[Resco Mobile CRM]] as your mobile frontend. Resco fully supports Dataverse's [[virtual table]]s, allowing you to access Business Central via Resco mobile apps.
+[[File:Businesscentral-dataverse-rescomobilecrm.png|600px]]
-== Use case: connect to Business Central ==
+== Resco mobility via Microsoft Dynamics ==
-You can use Integrations to connect to [[Business Central|Microsoft Dynamics 365 Business Central]].
+Business Central can integrate natively with '''Microsoft Dynamics 365 Field Service''' ([https://learn.microsoft.com/en-us/dynamics365/business-central/admin-integrate-field-service Microsoft documentation]). By installing [[Resco Suite]] to your Dynamics environment you can benefit from native integration between Resco and Dynamics and use [[Resco Mobile CRM]] as your mobile frontend. Resco fully supports Dataverse's [[virtual table]]s, allowing you to access Business Central via Resco mobile apps.
-=== Register Resco application in Business Central ===
+[[File:Businesscentral-dynamics.png|600px]]
+<!--
+== Resco mobility via Resco Cloud ==
-Before you can start migrating data between Resco Cloud and Business Central, you must register the Resco application (clientId) in Business Central and grant Resco consent with accessing Business Central data.
+If you want mobility for your Business Central without Dataverse/Power Platform/Dynamics, you can use [[Resco Cloud]] instead. It is a CRM server by Resco. It can connect to Business Central using one of the following methods:
-# Log in to your Business Central organization and go to the Azure Active Directory Applications.<br>[[File:Bc1.png|600px]]
+;Via [[Power Automate]] + [[Resco Cloud connector]]
-# Click '''New''' and fill out the registration form.<br>[[File:Bc2.png|600px]]
+: Full-featured integration using a '''third-party''' Microsoft service
-# As '''Client ID''', use <code>4abedb2f-19bc-402f-b0b5-b8d17e85aa04</code>.
+: [[File:Businesscentral-powerautomate-rescocloud.png|600px]]
-# Add '''User Permission Sets'''.
-# Grant the necesary consent.<br>[[File:Bc3.png|600px]]
-=== Install Resco extension on Business Central ===
-The extension is required for synchronizing between Resco Cloud and Business Central.
+;Using the [[Integrations]] feature of Woodford
-# Download the extension from [https://rescocloud.blob.core.windows.net/integrations/Resco_RescoIntegrations_1.0.0.0.zip Resco web].
+: Connect your Resco Cloud organization to Business Central '''directly''' from Woodford.
-# Log in to Business Central and search for "extensions".<br>[[File:Install extension 1.png|600px]]
+: [[File:Connect to business central directly from resco cloud.png|alt=Microsoft Dynamics 365 Business Central - Resco Scheme|600px]]
-# On the '''Manage''' tab, click '''Upload Extension''' and upload the zip file.<br>[[File:Install extension 2.png|600px]]
+: To read about the last option in detail, see [[Connect Resco Cloud to Business Central]].
+-->
+== Integration of Business Central and Dataverse ==
-=== Configure Woodford ===
+There are several ways in which Dataverse and Business Central can be integrated. Some of the interaction strategies are discussed in a video by the Microsoft's Business Central team:
-# Start Woodford and select '''Integrations''' from the '''Administrator''' menu.
+{{#ev:youtube|https://www.youtube.com/watch?v=-q8Gm7u7R2A|||||start=57}}
-# Click '''New''' and enter the following details:<br>[[File:Bc4.png|600px]]
-#* Name - enter a name of your integration
-#* Connector - select OData
-#* URL - enter the URL of Business Central OData endpoint (e.g., https://api.businesscentral.dynamics.com/v2.0/b8cc0002-2542-46ed-8584-d4868701fbc4/Production/ODataV4/)
-#* Username - BC account's email address
-#* Password - BC account's password
-#* CustomQueryParamaters - custom query, which should be added to the every request (e.g., <code>&company=CRONUS%20USA%2C%20Inc.</code>). It is important to include the correct <code>&company</code> parameter.
-# Click '''Save'''.
-Double-click this integration to map external entities/fields to local entities/fields.
+To summarize, the available integration options include:
+* '''Data Sync''' that replicates data changes between overlapping tables in Business Central and Dataverse
+* '''[[Virtual table]]s''' that enable interaction without data duplication
+* '''Data and business events''' that trigger [[Power Automate]] flows
-For Business Central, some settings are configured by default:
+It is important to realize that these different strategies can be combined. Some tables can be duplicated via data sync, other can stay virtual, etc. In addition to the methods listed by the Business Central team, various third-party solutions simplify integration between the two platforms. Ultimately, each project is unique and requires thought and expertise to succeed.
-* Default mapping will be added. In the preview, only three entities are officially supported: account, contact, and work order.
-* Based on default mapping, External Primary Key fields will be added to the schema.
-Verify that the three supported entities are enabled, save all changes, and you can start migrating or synchronizing data:
+Additional reading:
-* [[Integrations#Set_up_sync_filter|Set up sync filter]]
+* [https://learn.microsoft.com/en-us/dynamics365/business-central/admin-integrate-field-service Integrate with Microsoft Dynamics 365 Field Service]
-* [[Integrations#Import.2Fexport_data|Import/export data]]
+* [https://learn.microsoft.com/en-us/dynamics365/business-central/admin-common-data-service Integrate with Microsoft Dataverse via data sync]
-* [[Integrations#Synchronize_data|Synchronize data]]
+* [https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/powerplatform/powerplat-overview Microsoft Power Platform integration with Business Central via virtual tables]
-=== See also ===
+== Integration of Dataverse and Resco ==
-* [https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/webapi/discover-url-organization-web-api?view=op-9-1 Discover the URL for your Dynamics organization using the Web API]
+'''[[Resco Suite]]''' is a solution that you add to your Dataverse. It allows you to set up your mobile experience for Dataverse:
+* Select which tables, fields, and rows should be available in the Resco Mobile CRM app.
+* Design the home screen, views, forms, and more.
+* Add business logic to bind it all together.
+'''[[Resco Mobile CRM]]''' is the mobile app that grants you access to Dataverse data. This includes
+* Standard Dataverse tables
+* Dynamics 365 Field Service or Sales tables
+* Virtual tables of third-party systems such as Business Central or Finance & Operations
+* Custom tables designed by customer/partner
+* Custom tables by Resco (needed for extra Resco features such as [[inspections]] or [[Deep dive: Timesheets|timesheets]])
+== Bringing it all together ==
+The out-of-the-box integration between Business Central and Dataverse is gradually improving. Still, many customers prefer to supplement or replace it with a custom solution. What are some things to keep in mind?
-[[Category:Resco Cloud]]
+* Licensing - Make sure that you have all the necessary Microsoft licenses. Many integration scenarios require premium licenses.
+* Prepare for sync issues - Sooner or later, data will get out of sync. Plan ahead and prepare user-friendly and reliable tools and processes that business users can use even without technical knowledge. On Resco's side, we've got you covered with robust and highly configurable [[synchronization]]; [[sync log|detailed logs]], [[Sync Dashboard]], etc.
+* Standard or small - Standard scenarios involving field service or field sales generally work satisfactorily out-of-the-box. If you are working on a custom scenario, consider starting small so that the complexity doesn't overwhelm you.
+* Competent partner - ERPs are complex systems. Bring in a partner with integration expertise.
+* Ultimately, each project is different. Select the appropriate integration strategy. Duplicating the data might require re-implementing complex business logic in Dataverse (and possibly Resco Mobile CRM). Virtual tables bring their [https://learn.microsoft.com/en-us/power-apps/maker/data-platform/limits-tshoot-virtual-tables?tabs=sql own set of limitations].
+== Common scenarios ==
+What are some of the common scenarios involving Resco?
+* Use Resco's flexible platform to design a custom feature. For example, travel expenses management, with Resco as the mobile client for tracking expenses, scanning receipts, and uploading them to the back office for further processing.
+* Use some of Resco's popular features, such as digital forms (Resco Inspections) or timesheet management.
+* Use Resco as the mobile client for Dynamics Sales or Field Service.