Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 272 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Run in User Session Field in the Job Queue Entry table
jeqdev
Member Posts: 8
Hi,
I am using NAV 2015 with background posting and I have seen that the “Run in User Session Field” in the Job Queue Entry table is set to true. Having a look at the NAV Help doesn’t help much: “Indicates that the job queue entry will be processed in a session that has already been started by the user at the time the job was enqueued. This field is automatically updated.”.
1) I understand that when “Run in User Session” flag is true then the background posting is run as the same user that starts the job therefore NAV creates a new background session behind the scenes; When the flag is false then the job runs as the same user as the one that has started the job queue. Is it right?
2) I understand the benefits of having NAS (https://msdn.microsoft.com/en-us/librar ... 3(v=nav.80).aspx) . In a scenario with two NAV services -the default one and another one dedicated to NAS- when enabling background posting (“Run in User Session” field is true) I understand that NAV is going to start a new session in the default service. What is the benefit of having NAS in this scenario as the job would be run in the default instance?
Many thanks in advance.
I am using NAV 2015 with background posting and I have seen that the “Run in User Session Field” in the Job Queue Entry table is set to true. Having a look at the NAV Help doesn’t help much: “Indicates that the job queue entry will be processed in a session that has already been started by the user at the time the job was enqueued. This field is automatically updated.”.
1) I understand that when “Run in User Session” flag is true then the background posting is run as the same user that starts the job therefore NAV creates a new background session behind the scenes; When the flag is false then the job runs as the same user as the one that has started the job queue. Is it right?
2) I understand the benefits of having NAS (https://msdn.microsoft.com/en-us/librar ... 3(v=nav.80).aspx) . In a scenario with two NAV services -the default one and another one dedicated to NAS- when enabling background posting (“Run in User Session” field is true) I understand that NAV is going to start a new session in the default service. What is the benefit of having NAS in this scenario as the job would be run in the default instance?
Many thanks in advance.
0