Home » » What is BYOD in D365?

What is BYOD in D365?

What is BYOD in D365?

BYOD stands for Bring Your Own Database, a feature in Dynamics 365 Finance and Operations (D365 F&O) that allows customers to export data from the application into their own Azure SQL database. This feature enables customers to use their own database for various purposes, such as reporting, analytics, integration, or backup. In this article, we will explain the concept of BYOD, how to set it up, and what are its benefits and limitations.

Concept of BYOD

D365 F&O has three data stores: the primary database, the secondary database, and the entity store. The primary database is the operational database that stores all the transactional data and business logic. The secondary database is a real-time replicated database that supports the application performance and scalability. The entity store is an operational data warehouse that stores aggregated data for reporting and analytics using Power BI.

Data entities are abstractions of the underlying tables that group data into logical units. For example, a vendor entity contains information from multiple tables, such as vendor ID, name, address, contact details, etc. Data entities are used to expose data to external systems or tools via OData services or data management framework.

BYOD is a feature that allows customers to export data entities from D365 F&O into their own Azure SQL database. Customers can define one or more SQL databases and select which entities they want to export. They can also choose whether to export all the records (full push) or only the records that have changed or been deleted (incremental push). They can use the batch framework to schedule periodic exports or trigger them manually.

The BYOD database can be accessed by using Transact-SQL (T-SQL) and can be extended by adding more tables or views. Customers can use the BYOD database for various scenarios, such as:

  • Exporting data into their own data warehouse for advanced analytics or reporting using tools other than Power BI.
  • Integrating data with other systems or applications using batch processes or ETL tools.
  • Creating backups or archives of historical data for compliance or audit purposes.

How to set up BYOD

Before setting up BYOD, customers need to create an Azure SQL database by using Azure portal. They need to specify the server name, database name, pricing tier, and other settings. They also need to configure the firewall rules to allow access from D365 F&O and other sources.

To configure BYOD in D365 F&O, customers need to follow these steps:

  1. Go to System administration > Data management workspace.
  2. Select Configure Entity export to database tile.
  3. Click New to create a new connection.
  4. Enter a name and description for the connection.
  5. Select Azure SQL Database as the type.
  6. Enter the server name, database name, user name, and password for the Azure SQL database.
  7. Click Validate to test the connection.
  8. Click Save to save the connection.

After creating the connection, customers can select which entities they want to export to the BYOD database. They can do this by following these steps:

  1. Go to System administration > Data management workspace.
  2. Select Export tile.
  3. Click New to create a new export project.
  4. Enter a name and description for the project.
  5. Select Add entity to add one or more entities to the project.
  6. For each entity, select the connection name, destination table name, refresh type (full/incremental), and filter criteria (optional).
  7. Click Save to save the project.

After creating the project, customers can run it manually or schedule it using batch jobs. They can also monitor the status and progress of the export jobs by using the Execution history page.

Benefits and limitations of BYOD

BYOD has several benefits for customers who want to use their own database for reporting, analytics, integration, or backup purposes. Some of these benefits are:

  • BYOD provides more flexibility and control over the data structure and format in the external database.
  • BYOD supports T-SQL access to the data, which enables customers to use various tools and technologies that require T-SQL queries.
  • BYOD allows customers to combine data from D365 F&O with data from other sources in their own database.
  • BYOD enables customers to create backups or archives of historical data for compliance or audit purposes.

However, BYOD also has some limitations that customers need to be aware of before using it. Some of these limitations are:

  • BYOD requires additional cost and maintenance for creating and managing the Azure SQL database.
  • BYOD does not support real-time or near-real-time data synchronization with D365 F&O. The data in the BYOD database may be outdated depending on the frequency and timing of the export jobs.
  • BYOD does not support complex data types or relationships that exist in D365 F&O. For example, hierarchical data, composite keys, or many-to-many relationships may not be exported correctly or may require additional processing in the BYOD database.
  • BYOD does not support all the data entities that are available in D365 F&O. Some entities may not be exportable or may have performance or security issues.

Conclusion

BYOD is a feature in D365 F&O that allows customers to export data from the application into their own Azure SQL database. This feature enables customers to use their own database for various purposes, such as reporting, analytics, integration, or backup. However, BYOD also has some benefits and limitations that customers need to consider before using it. Customers should evaluate their business requirements and scenarios and choose the best option for their data needs.

0 মন্তব্য(গুলি):

একটি মন্তব্য পোস্ট করুন

Comment below if you have any questions

Contact form

নাম

ইমেল *

বার্তা *