In order to allow me to focus on Consulting (click here) and Courses (click here), I continue to review all posts here in the Forums, but, in general, I'm only personally responding to posts that I mark as #AcumaticaTnT (click here). For Questions (click here), others may respond, or you can post over at Community.Acumatica.com (click here).
Questions Business Event not triggering
I had set up a business event based on a generic inquiry filtered to show only shipments where the ship-to phone number is blank. The business event was set to run for New Record Inserted and would then run an import scenario to add our company's phone number to this field (this is to avoid issues with creating labels through the Fed-Ex integration where that is a required field). This was working well for the past couple months but then suddenly about a week ago it stopped triggering the events when new shipments are created. In checking the shipments are showing on the generic inquiry results still it just isn't triggering the event for some reason. Has anyone else run into any similar issues of events not triggering correctly?
The business events that are triggered on a record change are very temperamental and don't always work. If you are using 2018 R2 make sure you are on the latest build because Acumatica has been working to fix some of the issues. For some of our clients I have used the run on schedule to get the process to work consistently. Unfortunately, using the run on schedule usually requires an import scenario to also update some sort of flag to make sure emails aren't sent over and over.
We haven't upgraded or put any new clients on 2019 R1 yet so I'm not sure if it runs any better. I would recommend searching the known issues section on the Acumatica portal. https://portal.acumatica.com/release-notes/known-issues/ There are a couple issues regarding business events that are fixed in certain versions and some that have workarounds. Maybe one of them applies to you and you can figure out a way to work around the issue.
Been wondering why on after creating a business event to update case status and send email notification it would trigger record change for the top most record when it runs for the first time. I have been affected twice now after configuring this yet the record that has been affected has its status not matching my condition. My configuration is as below.
So the Business Event is picking up a record that doesn't meet your TRIGGER CONDITIONS?
Try changing your Raise Event to 'For Each Record'. That should run your event for all records in the inquiry.
We are having an issue in 19r1 creating a credit memo with multiple tran lines with a business event triggered by record insertion in a GI.
We have tried various settings, and the record add in the GI either does not kick off the event at all, or it only creates the first line. Because we need it to trigger on record insertion (a certain type of new invoice document is created), we cannot schedule that I can see.
Has anyone executed a scenario like this where multiple lines create one transaction with detail?
That Automation Schedule clue is interesting @megan-perry.
I personally haven't dug into the depths of Business Events to understand how they get triggered and what carries out the action. Is it done entirely by IIS or is there some Windows Service involved? Where are all the places that you need to check for error logs? I'd love to dig into it at some point, but I know that it will be involved.
I'd love to see any good documentation that anyone has found.