Strange issue with Business Event not firing if the underlying GI has a conditional on it. Worked through all the troubleshooting guides I could find, and still stumped. I have a Generic Inquiry which is a simple join of the AMMTran table and the AMProdItem table:The relations are simple, just joining the shared keys of OrderType and prodOrdID: And my conditions are straightforward, looking for Materials documents that linked to Closed production orders: And my business event is set to “Trigger by Record Change” with Raise Event set to “For Each Record”:This does not fire. If I change my conditions on the GI to remove the status=Completed, it works fine (though it fires immediately upon issue of the materials, which is NOT what I need, as I need to do something with the Material once the Production order completes). I have tried it with “from schema” for the condition instead of the =’M’, so it’s not anything that simple. I’ve tried changing the Trigger conditions to be Record Inser
Trying to enhance the AM613000 report to include our Legacy Part number on the report (this was implemented as a usr field on the InventoryItem table) It won’t let me join InventoryItem to AMMultiLevelBomData as I gather that AMMultiLevelBomData is a dynamic “table” based upon the answers to the questions on the AM413000 screen So how can I extend that to add a simple field? I assumed it should be as simple as adding the InventoryItem table to the report and joining on the InventoryID columns, but that errors.
When you add material to a BOM it will default the material line description to the then-current description from the stock item.(we leave it in our process) If that stock item’s description is subsequently updated it does NOT change the description on the BOM. While I understand why this is (the BOM description is technically a unique description of that stock item on that BOM, not a reference back to the stock item’s description) Is there a simple way to “refresh the BOM descriptions from the current stock item descriptions”? Thanks! -Matt
A positive inventory adjustment made directly to a project/task hits the project ledger as a negative qty/cost on the project ledger…. everything else in the GL and IN modules appears correct, but the project ledger is wrong. the workaround it to do the adjustment to project X (this avoiding the incorrect project transaction) and doing a transfer into the project… but in current release of Acumatica (22R1 and prior) this doesn’t completely solve the issue from a reporting standpoint, since transfers still don’t hit the project ledger at all…. would be nice to have that fixed btw… I have a business event setup to properly create a project transaction after the transfer.But this seems to be a legit a bug unless I’m missing something obvious… -Matt
I’d like to have a $ (dollar sign) included on the resultant line for a field in a GI.Can this be done? I understand about using the schema field to force a sort of inheritance around the field formatting, but what happens if you don’t have a field with the proper schema formatting? (I can’t find one that has the equivalent of $#.00) I only need the dollar sign $ but it would seem that it should support localizing in system currency. I know how to do this in Report Designer -- I need it to be in the Generic Inquiry (and hopefully a resultant Dashboard widget from there) thanks
I have a workflow action which I’m using to update the NoteText after transition from the state So the New Value is set to the following in the workflow > state > transition properties: {Set Field NoteText} =Concat('XXXXXX happened at ', Now(), CStr('\r\n') )Works like I would have expected, but that also over-writes the current note. The hope would be to append, so I attempted this: {Set Field NoteText} =Concat([NoteText], 'XXXXXX happened at ', Now(), CStr('\r\n') )This doesn’t behave any differently. How do I reference the current/existing note on the current document (in this case on the POReciept)? That way I can properly append my “log” entry. ALSO: does anyone else experience a bug in the note updates where you have to refresh the screen to see the new result, as opposed to just opening the note to see the current value?? PS: This approach isn’t what I’d really like to do, as I’d prefer to have a more generalized audit log mechanism that would work like the manufacturin
I’d like to do a similar thing in a couple of places, but right now I have a Business Event that fires whenever I make an inventory Transfer. That Business Event then triggers an Import Scenario that reads the lines from the Transfer and creates a Project Transaction (in this case, it creates a transaction with two lines, as I need to update the “From” Project/Task and the “To” Project/Task). My problem is I get a new Project Transaction for every line on the Transfer. Ideally I’d like to have a 1:1 correlation between the underlying Transfer and my created Project Transaction. Is this doable? I guess I’m essentially trying to loop/iterate within the import scenario. But because I need to create two lines from every input line, I’m not sure how to make it work. Import Scenario looks like this: Thanks!-Matt
Screenshot of Business Event status screenCurrently the Business Events screen has the “Execution Result” column -- is there a way to programmatically update that with text from the import scenario side of things? It would be nice to have details in the log about which event fired for what batch/transactions and when. thanks
We've done enough testing of this (trying to find a work around) that it's pretty clear what is happening is a bug and not a misconfiguration/misunderstanding. We already have a support ticket open, but I wanted to share out situation in case anyone else might be unknowingly having the same symptoms. Problem appears to occur when the *pay period* crosses the calendar year boundary. This is because Acumatica breaks it up into two PTO bank records - a 2021 portion and a 2022 portion. Then the PTO allocated is pro-rated across the payroll week... so in our scenario, with a payroll week from Monday-Sunday, two days are in 2022. And so our notional 1.54hr PTO weekly accrual gets split into a 2021 portion (1.1hrs) and a 2022 portion (.44hrs).On that first paystub of the year, we see ONLY the .44hrs allocable to 2022 reflected (same in the PTO Details by Employee Report -- though on THAT report you see the 2021 record broken out, it just isn’t summarized correctly.. I can live with that b
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.