We are going to be looking at how to set up a build-your-own-database (BYODB) in your Microsoft Dynamics 365 Finance and Supply Chain Management (D365 FSCM) cloud hosted tier 1 development VM.
First, go to SSMS and create a new database, VMBYODB.

Then, under Security > Logins, choose to create a new user, byodbadmin. Note the password here as it will be needed later.

Right click this user and select properties. Navigate to User Mapping > VMBYDOB and set the user to have the db_owner role. Additionally, under Server Roles include serveradmin.

Next, open up the D365 front end and navigate to the Data Management Workspace. From here select the “Configure entity export to database” tile.

Create a new record, VMBYODB. Enter the connection string in the following format:
Data Source=serverName;Initial Catalog=databaseName;Integrated Security=False;User ID=userid;Password=***
Make sure to validate the connection after entering the connection string.

After the connection is valid, select “Publish.” Here we can choose which entities we want to publish to our BYODB database. I selected the Customer groups entity and clicked “Publish.” This kicked off a batch process, which when complete, we can see the entity marked as published here.

At this time we can also head back to SSMS and confirm the entity’s staging table is now visible in our VMBYODB database. However, data has not yet been exported so this table contains no records.

To populate our table with data, we need to run an export job. We can set our export job up with the target data format set to our BYODB connection like so:

Then we can run the export job as normal, and upon completion our tables in the VMBYODB database will be populated with our data! We can then set up our export jobs on a recurrence to refresh the data at our desired cadence.
For more D365 F&SCM expert advice, contact us today.
Post originally published here: https://markedcode.com/index.php/2024/01/24/d365-byodb-in-tier-1-dev-vm/
This publication contains general information only and Sikich is not, by means of this publication, rendering accounting, business, financial, investment, legal, tax, or any other professional advice or services. This publication is not a substitute for such professional advice or services, nor should you use it as a basis for any decision, action or omission that may affect you or your business. Before making any decision, taking any action or omitting an action that may affect you or your business, you should consult a qualified professional advisor. In addition, this publication may contain certain content generated by an artificial intelligence (AI) language model. You acknowledge that Sikich shall not be responsible for any loss sustained by you or any person who relies on this publication.