Job Queue Entries record gone if error
julkifli33
Member Posts: 1,100
Hi All,
I am using nav 2017
I use job queue to complete line actions (IC posting)
but sometimes user careless, then they will send twice from sales to ic outbox (so become redundant)
my question is... usually my job queue if not successful, then the status for job queue changed become Error
but now it's gone
meaning there is no error status, but my job queue entries gone
Did I do something wrong for this job queue?
Thanks
I am using nav 2017
I use job queue to complete line actions (IC posting)
but sometimes user careless, then they will send twice from sales to ic outbox (so become redundant)
my question is... usually my job queue if not successful, then the status for job queue changed become Error
but now it's gone
meaning there is no error status, but my job queue entries gone
Did I do something wrong for this job queue?
Thanks
0
Best Answer
-
Is the field "Recurring Job" set to TRUE on the Job Queue Entries you are missing?
We use Recurring Job Queue Entries quite heavily in our system, and after upgrading to 2017 we found entries were being deleted. It was due to this function in Codeunit 453:
RemoveFailedJobs(JobQueueEntry);
We had to customize this function, adding this line:JobQueueEntry2.SETRANGE("Recurring Job", FALSE);
This solved the issue for us.
5
Answers
-
You didn't anything wrong. That's just the way it works. The background posting will remove all failed Job Queue Entries of the same record to post."Money is likewise the greatest chance and the greatest scourge of mankind."0
-
some status are changed become error
some are just disappeared.0 -
Yes, that's what I mean. If you re-trigger background posting for the same record, it will remove all the fails."Money is likewise the greatest chance and the greatest scourge of mankind."0
-
Is the field "Recurring Job" set to TRUE on the Job Queue Entries you are missing?
We use Recurring Job Queue Entries quite heavily in our system, and after upgrading to 2017 we found entries were being deleted. It was due to this function in Codeunit 453:
RemoveFailedJobs(JobQueueEntry);
We had to customize this function, adding this line:JobQueueEntry2.SETRANGE("Recurring Job", FALSE);
This solved the issue for us.
5 -
Hi robbonick ,
thanks a lot
this solve the issue!0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 611 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions