This tool is an experiment on Dynamics 365 Business Central with the sole purpose of discovering the possibilities of having data exported to an Azure Data Lake. To see the details of how this tool is supported, please visit the Support page. In case you wish to use this tool for your next project and engage with us, you are welcome to write to bc2adls@microsoft.com. As we are a small team, please expect delays in getting back to you.
The bc2adls tool is used to export data from Dynamics 365 Business Central (BC) to Azure Data Lake Storage and expose it in the CDM folder format. The components involved are the following,
- the businessCentral folder holds a BC extension called
Azure Data Lake Storage Export(ADLSE) which enables export of incremental data updates to a container on the data lake. The increments are stored in the CDM folder format described by thedeltas.cdm.manifest.json manifest. - the synapse folder holds the templates needed to create an Azure Synapse pipeline that consolidates the increments into a final
dataCDM folder.
The following diagram illustrates the flow of data through a usage scenario- the main points being,
- Incremental update data from BC is moved to Azure Data Lake Storage through the ADLSE extension into the
deltasfolder. - Triggering the Synapse pipeline(s) consolidates the increments into the data folder.
- The resulting data can be consumed by applications, such as Power BI, in the following ways:
- CDM: via the
data.cdm.manifest.json manifest - CSV/Parquet: via the underlying files for each individual entity inside the
datafolder - Spark/SQL: via shared metadata tables
- CDM: via the
More details:
- Installation and configuration
- Executing the export and pipeline
- Creating shared metadata tables
- Watch the webinar on bc2adls from Jan 2022
This project is constantly receiving new features and fixes. Find a list of all major updates in the changelog.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.