Sessions, Tasks or Job Queue, what to use in AL and Business Central?

Find more information at my blog www.hougaard.com or follow me on / ehougaard
Source code can be found here: github.com/hou...

[@hadtogiveyouacareertodestroyit]

Nice one Eric, it would be really awesome if you do videos for all of them.

[@TheJulietteCharlie]

It’s all about the specific requirement in a particular use case. You shouldn’t use background flows because you can. As programmer you must be aware, that you leave flow of control on a piece of code. If your function (and it’s callers) do not rely on results, then go for startsession. TaskScheduler gives by design feedback (Callbacks) of the result. JobQueue does by throwing events you can subscribe. And JobQ sends failures to user‘s Role Center if setup adequately. JobQ does retry automatically, if setup. But on failures you cannot unlike TaskScheduler define a certain Codeunit you want to address for post processings or clean ups. I got issues with TaskScheduler on different server instances on a database.

[@eduschimu]

Good video! I would be interested in a deep dive of StartSession

[@Stefan_21]

Hi Erik! I would like to see a video about SessionStart(). Especially about proper error handling when using it.

[@davidhofschneider7842]

Please deep dive to all of these options

[@thomastarp]

Agreed 😊

[@GooseMugs]

Erik you're videos are always bred ymer! Have you ever run into issues with the rate limitations of BC's API's? (i.e 600 req/min) If so what have you done to mitigate that?

[@erproerpro903]

Good stuff Erik!

[@robertkirsten2990]

Hi Eric, great video! How did you open the layer which tells you what param to put next into the function call at 5:33? I am desparately in need of this. :)

[@Hougaard]

Shift+ctrl+space

[@sowmyasridhar77]

Nice video Eric! We are using BC 22 On Prem. We are new to BC (still in the implementation stage). We have custom reports and codeunits scheduled in the job scheduler. I have set to run once in 5 minutes. It is not triggering the job to run automatically. It works fine when I click "Run Once (foreground)". Do we need to change anything in the sever (NASStartupCodeunit and NASStartupMethod)? I don't know if we are missing anything. Do we need a separate NAS service like NAV 2016 (we don't have a separate NAS Service in BC)?

[@Hougaard]

You don't need a separate nas service with bc22. "NAS" is not longer used.

[@sowmyasridhar77]

@@Hougaard Thank you Erik. I am not sure what am I missing. It is not running automatically. Do I need to specify /update any parameters in the Server?

[@Hougaard]

Make sure your service tier is configured for background sessions and tasks: learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/configure-server-instance#PBT

[@joy9497]

how does microsoft manage the resources since BC cloud has a fixed rate users and if we are using sessions it's going to use more resources to compute? is there also a duration limit per session which stops the session/process if they exceed the duration limit? Great video by the way.

[@Hougaard]

8 hours.

[@radojkica]

@@Hougaard In my case, I get a timeout after 6 hours. I have a report which takes 10 hours to finish. When the user runs it, I create 3 job queues in the background with the use of the Parameter String field to pass 3 different filters. What would you recommend in this situation? The report cannot be optimized, meaning it cannot be finished in one session.

[@RubenParente]

Hi Eric, i know this is not the best video for it. But i would like to ask you if you know something about microsoft killing BC onpre. wht are your thoughts about it. thank you

[@Hougaard]

They're not, but the onpremise version will continue to be the lesser version. When people stop buying it they will stop selling it... But they still sell GP so....