Finance | Project Operations, Human Resources, ...

Does anyone know how Document Routing Agent communicates to D365?

(0) Share

Report

Posted on by matt.barys

Hi All,

Have a question about the document routing agent and communications with D365. We are a hyper seasonal company where most of our business takes place within a two week period before Christmas. During this time, we have 19 scan stations in our warehouse scanning barcodes on packages and printing shipping labels for those packages. So the flow in my mind is (from the confirmation page in D365),

-Scan the label from the confirmation page (Container number)

-D365 pulls back info and sends it to our Proship server

-Proship sends the labels image back to D365

-DRA scans every 5 seconds for new print jobs

-Label prints out

That's all fine and dandy any other time of the year where we can ship out 100-200 packages a day, but during the two weeks, we can ship out 30000 a day.

My real question here is how the DRA communicates with D365 to get the info. Odata? Https?

The reason we are asking is because last year several times, the DRA's would get stuck on "Checking for next document" for minutes at a time. If we had 3 DRA's going, all three would be stuck at the same time rendering printing useless.

We are just trying to figure out why these would all freeze at the same time and any input would be great!

Thanks

I have the same question (0)

All responses (6)

Answers (0)

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Matt,

I do think it makes sense if you try to reach out to Microsoft Directly. Probably there are volunteers on this forum with partly knowledge what you are asking. As this is critical for your business it would be good to ask questions and for sure create support incidents when the DRA's get stuck or can't meet the required performance.

Was this reply helpful? Yes No
matt.barys 5 on at

Like (0)

Report

Yeah. Our first real question was to see if someone knew the data transporter for this. We think it's Odata which could make sense. I may try to reach out to them but we can't reproduce it until busy season and by that time it's too late and we are losing time and money.

Thanks

Was this reply helpful? Yes No
FahadAhmed 205 on at

Like (0)

Report

Hi Matt - even if you know what technology they use, you wouldn't probably be able to sort out the issue yourself. As we are pretty much dependent on the DRA tool for printing. I am guessing you are running it as a service through a print server? We have noticed better response time when we run it as a service and divide the printers among multiple print servers.

regards,

-Fahad

Was this reply helpful? Yes No
Suggested answer

Eugen Glasow 6,359 on at

Like (0)

Report

My impression was the "checking for next document" was an ODATA call. Once a new document is ready, the ODATA call returns something and the DRA executes a HTTP GET to download the PDF file from the Azure blob like a usual attachment.

Was this reply helpful? Yes No
matt.barys 5 on at

Like (0)

Report

Thanks for the responses. This gets us on the right track to investigate!

Matt

Was this reply helpful? Yes No
Martin Dráb 237,882 Most Valuable Professional on at

Like (0)

Report

Consider using something like Fiddler to observe the communication.

Was this reply helpful? Yes No