I think I was able to get the information I needed to resolve the customization issue.Audit history definitely isn’t the easiest thing to work with.
@jgress Your post is fantastic. It did a good job of highlighting the uses and limitations of the data that Acumatica collects.With the data available I found that the audit history access screen data has been the most useful for me. User adoption of a particular screen/report could be easily gauged with a quick pivot on the Access Screen audit history. It really helped highlight gaps in training since I could see how often a user was accessing a screen and could see if a user wasn’t aware of a screen that their peers were using regularly.Really wish I knew about this when we were implementing. Would have made the transition much smoother since we had a lot of users getting lost/frustrated/creative when a solution to their problem already existed.
We just went live with Korber at the end of June 2023. It’s been a rocky start, but we’re working through the issues. I’d be happy to meet with other Korber users - feel free to reach out to me at ncantral@wilmarllc.com.
Looking back, I misunderstood the original post. Since the stock and non-stock components exist on separate tables we would need to get creative since union operators are not supported natively (if I recall correctly).Customization is always an option. Subreports would be more accessible but loses out on the great functionality of GIs. Simplest option would be to join the non-stock detail to the stock detail on KitInventoryID, RevisionID, and LineNbr. This assumes you always have more stock items than non-stock on a given kit. Not my favorite solution since it’s not the best user experience having the data organized like this. Below is an example:
Training - I have never heard someone complain after a go-live that they trained too much. Getting repeated, hands-on experience with real scenarios in a sandbox environment is the best thing you can do for your users. They’ll get familiar with processes, ask questions, and build confidence. These are all critical to user adoption. It’s also an opportunity to test your processes. As users wander through the system, they’ll find gaps and identify areas that need to be addressed.For third party integrations – have a plan for auditing that Acumatica and the other system are in sync. How will you know if a transaction didn’t flow back to Acumatica? How will you fix a discrepancy between the two systems?Users – patience and compassion will go a long way. This can also be an incredibly stressful event for your users. Change can be difficult, especially if you are moving away from a familiar legacy system or dramatically altering someone’s role. Check in with users (not just trainers and supe
This is an old post but if anyone else followed the instructions above and doesn’t see the expected changes - don’t forget to enable to the new workflow after adding it. Took me longer than I care to admit to figure that out.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.