Datasets and Connectors Explained | Azure Data Factory for Business Central

Before a pipeline can move anything, it has to know what it is moving and where from. That is what a dataset is, and it is the piece most people skip past. Alex walks through the connector library in Azure Data Factory, configures an Oracle connection end to end, tests it, and builds the matching destination dataset on Azure SQL. This is the layer that sits underneath every migration into Microsoft Dynamics 365 Business Central. What is covered: 0:00 Intro 0:13 What a dataset is 0:27 The connector library 1:03 Not every ERP needs its own connector 2:20 Configuring the Oracle connector 4:09 Testing the connection 4:39 Selecting the source table 6:40 Creating the destination dataset 8:31 Connecting to Azure SQL 9:53 Selecting the destination table A dataset defines the source or destination a pipeline works with. A connector is how Data Factory reaches the system it lives in. Azure Data Factory ships with a large library of them, and one of the useful things about that library is how often you do not need a dedicated connector at all. A generic protocol connector reaches plenty of systems that never got a named tile. Part 1 covers the solution and how pipelines are monitored. Part 3 covers copy data, lookup and record processing. Not sure whether your ERP is ready to move? Free ERP Readiness Scorecard: https://erp-readiness-scorecard.verce... More: https://www.navisiontech.com Navisiontech is a Microsoft Solutions Partner. We implement, migrate and support Microsoft Dynamics 365 Business Central, LS Central and the Power Platform for wholesale distribution and retail. #BusinessCentral #Dynamics365 #AzureDataFactory #ERPMigration #DataMigration