Automatic posting in other entities

sneha

Here is the scenario:

We’ve totally 6 companies in our system Nav 4.0 (sql server is the db). There is one similar general journal batch called “MonthPost” in all of the 6 companies (batch is same but, journal entries are different though). Currently, we’ve to get into each of those 6 companies to post the batch. Wondering is there a way to post the batch automatically in other entities when I post in one entity?

sneha

No easy way to hit the button automatically in other entities when a user hits a post button in one entity?

einsTeIn.NET

I would use (maybe a recurring) Job Queue Entry in each Company. You probably need to update (at least) the Job Queue module as it became a lot more stable in 5.01, if I remember correctly.

bbrown

The "Job Queue" was not available in version 4. In version 4 you had "Job Scheduler" which ran as a client process and not on NAS.

sneha

I doubt either job queue (or) job scheduler is a trick here because, we want to trigger the post button in other entities only when it got posted in one entity. For example, we've 6 entites. When a general journal is posted in entity#2 then we want the system to auto-post the same general journal batch in the remaining entities#1,#3,#4,#5 and #6.

vaprog

So, just check the condition before posting in the jobs.

An entirely different approach may be to launch a batch of navision:// hyperlinks from the initiating entity.

bbrown

sneha wrote:

I doubt either job queue (or) job scheduler is a trick here because, we want to trigger the post button in other entities only when it got posted in one entity. For example, we've 6 entites. When a general journal is posted in entity#2 then we want the system to auto-post the same general journal batch in the remaining entities#1,#3,#4,#5 and #6.

I don't agree. You could build something along these lines using Job Queue, or better yet standalone NAS sessions. You just need to give some thought to the design. One issue would be how you handle a failed transaction.

einsTeIn.NET

The problem is that you can't really just use CHANGECOMPANY function as there might be some VALIDATE or function calls that would be executed in your current company. So, basically you would need some process that is executed in those companies where you would like to post the same journal. You have to be aware of that any action in other companies won't be executed immediately (within the same transaction) but a little time shifted. That means either periodically time scheduled or e.g. when the next user opens that company. But I think that's acceptable in your case, although in the end you have to decide what's the best solution as it depends on your business case.