We have a functions library for job-specific functions that already uses JobStatus for a couple functions. I’m creating a function to release certain jobs, but I noticed in the trace log that Epicor uses JobEntry to release the jobs. However, adding JobStatus and JobEntry to the same library will throw an error where both tables have the same type of JobHeadListTableset when I use GetList.
My question is what is the difference between these two tables and when should I use either? At a quick glance they seem to be almost identical.
My assumption would be that JobEntry would be used in the creation of jobs (creating new Job records). JobStatus would be used when manipulating transactions that hit against those records.
This was my initial thought, it’s just the trace log showing JobEntry to release a job that sparked my curiosity, I’m wondering if there are weird differences that might affect the function.
I’ve successfully used the JobEntrySvc to make changes on existing Jobs before, but I haven’t used JobStatus so I can’t say which is better. Tracing changes to jobs from the Job Entry module seems to use JobEntrySvc for most changes to JobHead / JobProd level changes.
Right, I think JobEntrySvc would be used to alter the job records (JobHead type fields).
But to me, JobStatus seems to point more towards records against those jobs, like material transactions, labor transactions, etc. Again, this is only my assumption and am probably completely wrong.
I agree, I’ve never actually seen the JobStatus service used at all.
@JoeEpicor , what kind of things are you doing with those current functions against JobStatus? Just curious.
That makes sense.
The current functions work together to change the ReqDueDate on jobs with a ReqDueDate of the current date or a date in the past to the next business day, one calls the other and logs the successes/errors for an email.
I didn’t create these so I couldn’t tell you about more of the specifics off the top of my head.