Insert Sage 300 Order Detail New Line - Ignoring LineNum value assigned (3 replies and 1 comment)
Hi Sue,
You've taken the right approach, I'll try and replicate on our test rig, I'll be in contact once I have something definite for you.
Nick
Nick, any luck on this? Just checking in to see if you have found a solution or work around. The client really needs this misc charge to show at the bottom of the order, if possible. thanks much! Sue
Nick, checking in again on this - I still need this to work. do you have a fix for me? thanks!
Sue, apologies for dragging our feet on this.
As you've seen the new detail lines are being inserted as various random points.
We will provide you a fix by your Wednesday.
I built an Iman v3.2 job that reads an existing order in Sage 300 2017, and then inserts a new misc charge line on the order. I created an aggregate record and set all of the field values correctly for my misc charge. The job inserts the record into the order, but it is ignoring the Line number that I assigned.
I want the misc charge to be the last detail line on the order, so that customer service easily sees it. So I calculated the Maximum Line Number for the existing detail lines and then said that the new misc charge line number should be the Max + 32. I can see in the preview, that the Line Number assigned to that record is 3,520. I have mapped this value to the LINENUM in the Sage 300 connector. But when I run the Sage 300 connector refresh - the line number it assigns is 40 (regardless of whether I run it in the Iman job preview or schedule the job. I verified this by running a SQL query after the misc charge is inserted.)
So then I thought maybe I could assign the DetailNum instead of the LineNum but that isn't an option in the Sage 300 connector. What am I missing? thanks !
See attached screenshots including - the order before it was updated, the line number formula for the new misc charge, a preview of the line number I assigned, and the Sage 300 connector preview showing the line number Iman assigned.