D365FO On-prem exports to BYOD with ODBC connection

(0) Share

Report

Posted on by Celeste

307

Hi. We have an on-prem implementation. I want to export data to a BYOD (not an Azure SQL DB).

From information on how to export to BYOD I’ve found on various forums, I configured the datasource as ODBC in DataManagement.

I’ve also configured an entity export to db, using my ODBC datasource (the type was set and uneditable on the DMFDataSource form, but I personalized the form, added the type field again and was able to set the type to ODBC). The connection string to the BYOD validates.

I’ve published a standard entity and a batch job was created successfully.

The data “seems” to export successfully if I look at the history in data management. The staging table contains several records.

On the BYOD the new table was created successfully (which is the same as the staging table of the entity), but there is no data in the table.

I’ve run the same export multiple times. I’ve also published other entities to export to my BYOD with the ODBC connection. The staging tables create, but again without data.

I’ve tested the user I use in my connection string, and I’m able to create a record manually in the staging tables with the user.

My question: why are the tables created successfully in the BYOD, but no data is exported?

I have the same question (0)

All responses (4)

Answers (0)

Sort by

WillWU 22,363 on at

Like (0)

Report
Copy link

Link copied!

Hi Celeste Lategan,

In cloud, the infrastructure of Production is managed and hosted by Microsoft, and you have no direct access to it in any way.

Since your external DB will not be on the same network as your D365FO cloud deployment, you need an internet-facing external database to be able to access it via ODBC calls if that DB is sitting on your own infrastructure or private cloud.

For one-box development environments, you can create a database in the local Microsoft SQL Server database. However, this database should be used only for development and testing purposes. For production environments, you must create an Azure SQL database.

Refer to:docs.microsoft.com/.../export-entities-to-your-own-database

If you don't want to go with azure SQL db and want to connect to your own on perm db then you need some middleware.

Was this reply helpful? Yes No
WillWU 22,363 on at

Like (0)

Report
Copy link

Link copied!

Moved to D365FO Forum.

Was this reply helpful? Yes No
Celeste 307 on at

Like (0)

Report
Copy link

Link copied!

This is not a cloud environment, it is on-prem.

The connection to the database can establish, staging tables are created with configuring entity exports. However the data is not.

Was this reply helpful? Yes No
Ivan VULJAK 5 on at

Like (0)

Report
Copy link

Link copied!

Hi,

did you manage to solve this issue?

Best regards,

Ivan

Was this reply helpful? Yes No