Skip to main content



No record found.

Supply Chain Management forum

Sale order confirmation take too much time

Posted on by 31
Hello experts, 
I am facing a problem when generating a sale order confirmation. It takes 45s to generate the sale order confirmation even if I have only 1 line in my sale order. I have made the test on multiple customers, with differents items, ... but always the same issue.
I also tried to confirm the sale order without printing any document and it tooks the same time

I tried to do the same test on the same environment (UAT) but on another legal entity. It tooks 5s. The version is 10.39
Do you have any idea about a set up that could be the cause of this issue ? 
More generally, what happens in the background when we generate a sale order confirmation?
Thank you for your help ! :)
  • Valentin DORNIER Profile Picture
    Valentin DORNIER 31 on at
    Sale order confirmation take too much time
    Hello ! 
    Thank you very much for your answers. 
    The problem has been solved.  It was a selection step in the SQL database that was problematic. Our Microsoft partner resolved the issue. 

    Thank you again for your answers ! :)
    Best regards
  • Navneeth Nagrajan Profile Picture
    Navneeth Nagrajan 1,339 on at
    Sale order confirmation take too much time
    As Andreas mentioned, UAT environments (Tier-2) environment are allocated with more processing power compared to the Tier-1 environments. If the Sales order confirmation is taking 5 seconds in the UAT environment then expect much faster processing times in the Production instance too. 
    Happy to answer questions, if any. 
  • andreasraithel Profile Picture
    andreasraithel 4,596 on at
    Sale order confirmation take too much time
    typically the frist process (order confirmation) takes the longest time as the code has to be loaded and after the first load the code is cached and is more fast the second time.
    To compare Tiet 1 (Cloud hosted environment) and Tier 2 (UAT) is not really comparable as TRier 2 can have multiple instances, even the caching is the same as on Tier 1.
    For production (as well as for UAT) the recommendation from me ist to use batches to confirm, so all operations run in background, you do not need to care about runtime and it does not block your einvironment.
    Hope this helps.
    Herzliche Grüße / kind regards,
    Andreas Raithel
    D365FO Solution Architect

Helpful resources

Quick Links

Replay now available! Dynamics 365 Community Call (CRM Edition)

Catch up on the first D365 Community Call held on 7/10

Community Spotlight of the Month

Kudos to Saurav Dhyani!

Congratulations to the June Top 10 community leaders!

These stars go above and beyond . . .


André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 288,420 Super User

Martin Dráb Profile Picture

Martin Dráb 225,672 Super User

nmaenpaa Profile Picture

nmaenpaa 101,148


Featured topics

Product updates

Dynamics 365 release plans