If we create an inventory adjustment or void an inventory adjustment, it writes the change to the item ledger GL in NW currently.
If we want it to write a GL to another older dealership different system like DT DMS, would it be best to create after extension LB on WriteInventoryTransactionsToItemLedger LB and VoidItemLedgerTransaction LB to call an external endpoint definition OR an event? I assume endpoint definition? I don’t have much experience with events. Or, should we go about it differently?
I think it would revolve more around the target system’s capabilities - seeing if there is a limitation on either approach first.
If both business events and REST Endpoints work, then, it would be a question of timing. If you need the external accounting system to process before continuing on in your workstream, then it sounds like you would want to use more a request/response driven API - endpoint definitions - this would mimic how writing to Nextworld’s General Ledger will also work. If you want to process more asynchronously/ less dependent on the response or the GL posting successfully, then a business event would fit that use case better.
So an extension on the logic blocks in the existing code to call an external endpoint will work as a valid game plan.
Thanks! So, if Cox were to not have the NW accounting module, where would be the best place to intercept since we wouldn’t have access to WriteInventoryTransactionsToItemLedger anymore? An after extension on WriteInventoryTransactions? Sounds like we would have to create a common LB to call an external endpoint to write and hook it up to all functionality/ logic that would write to the GL.