Order Line Creation with Automation Studio

Kinetic ERP
,
1

I need to create a bunch (250+) of order detail lines, update the Release on each of those lines, and add a freight charge to each line. At the moment my data source is an Excel worksheet. I chose not to go the DMT route with this because while I’m adding 250+ lines, the system is adding a whole bunch of kit part lines. This makes it more complicated to update releases and add the misc charge via DMT since the line numbers I need to use in those subsequent processes aren’t sequential.

I’m adding my rows using api/v2/odata/IRP/Erp.BO.SalesOrderSvc/OrderDtls.

In a perfect world, the response from that call would be the record details for the record that I created. It’s not. The response I get will be the data from one of the component lines that the system created.

In a less than perfect, but ok, world, the record returned would the from the last component line created. I don’t live in that world either. In this experience, the system creates lines 2-11 and it returns the record for line 8. :man_shrugging:

My work around was to add a step after I create the order line to retrieve the order and then determine what the next line number will be. This worked, but caused the recipe to slow as the number of lines increased.

My next idea is to call a simple BAQ that gives me that maximum line number for the order instead of retrieving the whole order. This should minimize performance degradation as the number of lines grow.

Because of the seeming randomness of the record being returned when I create the line, I’m wondering if there’s a timing issue at play. Maybe if my Kit part has 20 components instead of 10, the system won’t be done creating all of those component lines when I query to find the last one. :thinking:

If that’s the case, the only idea I’ve come up with to get around this is to query to find the number of component parts for the kit before adding the line and then calculating the next kit parent line number from that.

Anyone got any better ideas?

2

A function to do the real work.

3 Likes
3

Is the idea here that the Update method won’t complete and allow the function to move on until all the component lines are created?

4

In a function, you are working with the tableset, so you can easily see what lines came back in your tableset. It gives you a lot more granularity and control than you get via automation studio.

1 Like
5

You could also not call generate kits add all the lines then call generate kits on each line after

That way you don’t hvabe to worry about the next line

Use the RPC endpoints not the oData

3 Likes
6

I did go down the path of building a function. Once I got through that, I was able to use Power Automate to read the data out of the Excel workbook and call the function for each line. After all the lines were entered, then I used a second function to generate the kits - once again driven by an Excel workbook and Power Automate. It’s not the most elegant solution, but is functional. Thanks for the tips. Unfortunately, can only mark one as the solution.

2 Likes