Sage 100

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

I'm thinking it might be that the SO is not in an editable state (allowing you to create an invoice from it) during the post-write event, blocking things at a higher level.  Did you check the retVal when setting the SO#?  Perhaps add debug comments script-line by script-line to see where in the line reading / writing that things are breaking down.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

This is what breaks my brain - when I add in the debugging, everything reports that it is happy - retVal = 1 across the board. and technically that is true, it is writing everything except it skips the OrderLineKey, debugging on that setvalue specifically is still 1.  I've wandered down some rabbit holes trying to just get that field to write!

I'm thinking it might be that the SO is not in an editable state (allowing you to create an invoice from it) during the post-write event, blocking things at a higher level.  Did you check the retVal when setting the SO#?  Perhaps add debug comments script-line by script-line to see where in the line reading / writing that things are breaking down.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

100%, you have to set OrderLineKey first.  Do not set the ItemCode.  Doing this will absolutely create a new line, unlinked to the SO... and you can't retroactively link a new line to an SO line.  The new line must start from the OrderLineKey. 

Your first oInvLines.SetValue needs to be OrderLineKey.

This is what breaks my brain - when I add in the debugging, everything reports that it is happy - retVal = 1 across the board. and technically that is true, it is writing everything except it skips the OrderLineKey, debugging on that setvalue specifically is still 1.  I've wandered down some rabbit holes trying to just get that field to write!

I'm thinking it might be that the SO is not in an editable state (allowing you to create an invoice from it) during the post-write event, blocking things at a higher level.  Did you check the retVal when setting the SO#?  Perhaps add debug comments script-line by script-line to see where in the line reading / writing that things are breaking down.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

@Kate Krueger - You mentioned:

>> The script is running on table post-write but I don't think the sales order is all the way written.

Correct. Unfortunately the lines have not been physically written to SO_SalesOrderDetail when Header PostWrite fires off. The lines data in still in a memory file. That is why when you revisit the order, the script does work. However, on an existing order if you add / modify / delete a line, those changes in the line will not get reflected when your PostWrite runs as it will work on the last copy of the lines you had.

Here are your options in order of definitely works to hmm maybe works. You may have tried some of this already:

1. Create a small mod as it can position itself to run after the Sage WRITE has completed. I've done that for this very reason.
2. Place your working script (a version that uses CopyLinesFromSalesOrder in another place) in some place other than S/O Entry screen. I know that defeats the purpose of the convenience of S/O Entry.
3. Create a Customizer button in S/O Entry but define it as a Perform Logic button. That pvx code can click the Accept button for you and keep on chugging to then create the Invoice.
4. Create a Customizer script button in S/O Entry that will conditionally:
   rV = oScript.InvokeButton("BT_ACCEPT") 'Let us hope the script continues to run after this.
   'If script continues to execute,
   'Now create the invoice if CurrentInvoiceNo$ is blank and prior to that you would do all other GetValue's you need.
   'Be sure to use CopyLinesFromSalesOrder when creating the invoice. Don't do all the manual lines work.
   

Hope that helps.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

Okay - closing the loop on this thread...sort of. I took @Alnoor Cassim's idea of having the script running on a different object/event and have a Frankenstein's monster routine that is 99% working. I added a UDT that is holding sales order numbers that need these invoices created (drop ship orders). I added a BOI script that independently goes through Sales Order bus and finds drop ship orders and writes the order number to the UDT. A post-write script on the UDT takes the order number and creates the invoice. This works except for one flaw - the last order added to the UDT does not successfully create the invoice. It stays in the UDT and is caught the next time the BOI is run but it is bothering me and I'll still probably chase that squirrel. But thank you for the help and I'm much closer!  

@Kate Krueger - You mentioned:

>> The script is running on table post-write but I don't think the sales order is all the way written.

Correct. Unfortunately the lines have not been physically written to SO_SalesOrderDetail when Header PostWrite fires off. The lines data in still in a memory file. That is why when you revisit the order, the script does work. However, on an existing order if you add / modify / delete a line, those changes in the line will not get reflected when your PostWrite runs as it will work on the last copy of the lines you had.

Here are your options in order of definitely works to hmm maybe works. You may have tried some of this already:

1. Create a small mod as it can position itself to run after the Sage WRITE has completed. I've done that for this very reason.
2. Place your working script (a version that uses CopyLinesFromSalesOrder in another place) in some place other than S/O Entry screen. I know that defeats the purpose of the convenience of S/O Entry.
3. Create a Customizer button in S/O Entry but define it as a Perform Logic button. That pvx code can click the Accept button for you and keep on chugging to then create the Invoice.
4. Create a Customizer script button in S/O Entry that will conditionally:
   rV = oScript.InvokeButton("BT_ACCEPT") 'Let us hope the script continues to run after this.
   'If script continues to execute,
   'Now create the invoice if CurrentInvoiceNo$ is blank and prior to that you would do all other GetValue's you need.
   'Be sure to use CopyLinesFromSalesOrder when creating the invoice. Don't do all the manual lines work.
   

Hope that helps.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

Okay - closing the loop on this thread...sort of. I took @Alnoor Cassim's idea of having the script running on a different object/event and have a Frankenstein's monster routine that is 99% working. I added a UDT that is holding sales order numbers that need these invoices created (drop ship orders). I added a BOI script that independently goes through Sales Order bus and finds drop ship orders and writes the order number to the UDT. A post-write script on the UDT takes the order number and creates the invoice. This works except for one flaw - the last order added to the UDT does not successfully create the invoice. It stays in the UDT and is caught the next time the BOI is run but it is bothering me and I'll still probably chase that squirrel. But thank you for the help and I'm much closer!  

@Kate Krueger - You mentioned:

>> The script is running on table post-write but I don't think the sales order is all the way written.

Correct. Unfortunately the lines have not been physically written to SO_SalesOrderDetail when Header PostWrite fires off. The lines data in still in a memory file. That is why when you revisit the order, the script does work. However, on an existing order if you add / modify / delete a line, those changes in the line will not get reflected when your PostWrite runs as it will work on the last copy of the lines you had.

Here are your options in order of definitely works to hmm maybe works. You may have tried some of this already:

1. Create a small mod as it can position itself to run after the Sage WRITE has completed. I've done that for this very reason.
2. Place your working script (a version that uses CopyLinesFromSalesOrder in another place) in some place other than S/O Entry screen. I know that defeats the purpose of the convenience of S/O Entry.
3. Create a Customizer button in S/O Entry but define it as a Perform Logic button. That pvx code can click the Accept button for you and keep on chugging to then create the Invoice.
4. Create a Customizer script button in S/O Entry that will conditionally:
   rV = oScript.InvokeButton("BT_ACCEPT") 'Let us hope the script continues to run after this.
   'If script continues to execute,
   'Now create the invoice if CurrentInvoiceNo$ is blank and prior to that you would do all other GetValue's you need.
   'Be sure to use CopyLinesFromSalesOrder when creating the invoice. Don't do all the manual lines work.
   

Hope that helps.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.

Crazy thought here and I know you're too far gone into this already, but instead of triggering a script off the UDT, maybe you can:

• Have your BOI directly create the invoice once it IDs a drop ship order instead of relying on the UDT postwrite? If that works, then use Windows Task Scheduler to auto-run the BOI.
• Optional: At the end of your BOI write the SONum to the UDT to indicate the invoice for it was created.
• Optional: At the beginning of your BOI check the UDT and skip invoice creation if your SO was found. But maybe you don't want that for situations where a SO is backordered and it's time to re-ship the backordered qtys.

Okay - closing the loop on this thread...sort of. I took @Alnoor Cassim's idea of having the script running on a different object/event and have a Frankenstein's monster routine that is 99% working. I added a UDT that is holding sales order numbers that need these invoices created (drop ship orders). I added a BOI script that independently goes through Sales Order bus and finds drop ship orders and writes the order number to the UDT. A post-write script on the UDT takes the order number and creates the invoice. This works except for one flaw - the last order added to the UDT does not successfully create the invoice. It stays in the UDT and is caught the next time the BOI is run but it is bothering me and I'll still probably chase that squirrel. But thank you for the help and I'm much closer!  

@Kate Krueger - You mentioned:

>> The script is running on table post-write but I don't think the sales order is all the way written.

Correct. Unfortunately the lines have not been physically written to SO_SalesOrderDetail when Header PostWrite fires off. The lines data in still in a memory file. That is why when you revisit the order, the script does work. However, on an existing order if you add / modify / delete a line, those changes in the line will not get reflected when your PostWrite runs as it will work on the last copy of the lines you had.

Here are your options in order of definitely works to hmm maybe works. You may have tried some of this already:

1. Create a small mod as it can position itself to run after the Sage WRITE has completed. I've done that for this very reason.
2. Place your working script (a version that uses CopyLinesFromSalesOrder in another place) in some place other than S/O Entry screen. I know that defeats the purpose of the convenience of S/O Entry.
3. Create a Customizer button in S/O Entry but define it as a Perform Logic button. That pvx code can click the Accept button for you and keep on chugging to then create the Invoice.
4. Create a Customizer script button in S/O Entry that will conditionally:
   rV = oScript.InvokeButton("BT_ACCEPT") 'Let us hope the script continues to run after this.
   'If script continues to execute,
   'Now create the invoice if CurrentInvoiceNo$ is blank and prior to that you would do all other GetValue's you need.
   'Be sure to use CopyLinesFromSalesOrder when creating the invoice. Don't do all the manual lines work.
   

Hope that helps.

Thanks for your reply Kevin! I'm thinking this may be the same issue that I was having with CopyLinesFromSalesOrder. When I take out all the SetValue on Item Code, Qty Ordered, etc. I get the error message "The Item Code is Required, The Item Type is required" etc. If I re-open the sales order and run the script again it works perfectly to create the invoice. So I'm thinking the OrderLineKey won't write because at that moment in time, the sales order doesn't have an OrderLinekey written to the table. The script is running on table post-write but I don't think the sales order is all the way written. Is there a method to complete the write and re-open the sales order? 

Don't SetValue on ItemCode to start the new invoice line... set the OrderLineKey... which should pull in the ItemCode. 

Think about how VI imports of invoice lines work, when invoicing an SO.  You don't import the fields that should flow from the SO lines.