Manuel,

Yes, that is possible. Below is the code that I use in PowerShell for the AP Invoice Register. But you can easily transform this for VBScript or C# and change the objects to the ones for SO.

$retVal = $oSS.nSetProgram($oSS.nLookupTask("AP_InvoiceRegister_ui")) 
$oAPInvReg = $oScript.NewObject("AP_InvoiceRegister_upd",  [ref]$oSS)
# .nBatchEnabled to test if Batch Processing is activated
$retVal = $oAPInvReg.nSelectBatch("12345")
if ($retVal -eq 1)
{
    $retVal = $oAPInvReg.nPDFSilent = 1
    $retVal = $oAPInvReg.nSetPostingDate("$sModuleDate")
    $retVal = $oAPInvReg.nProcessReport("PRINT") #DEFERRED
    $retVal = $oAPInvReg.nEndOfPDFConverterJob()
    $retVal = $oAPInvReg.nUpdate()
}

Hi Billy,

Thanks a bunch, i'll give it a try in PowerShell first,

I'll change the object to the SO Object.

Thanks again...

Regards,

Manuel

Hi Billy,

Thanks a bunch, i'll give it a try in PowerShell first,

I'll change the object to the SO Object.

Thanks again...

Regards,

Manuel

I have several examples on here about journals.  Also pretty sure one of them addresses using Paperless Office with it as well so they don't go to DEFERRED printing but actually hit Paperless Office.

Hi David,

Where ?

Regards,

Check this thread.  It has additional links to some other threads.

Updating Batches via BOI - Sage 100 Personalization, Customization, and Productivity Tools - Sage 100 - Sage City Community

Here are some additional links.

https://www.sagecity.com/support_communities/sage100_erp/f/sage-100-business-object-interface/169128/so_salesjournal_upd---the-register-must-be-printed-prior-to-posting/434986#434986

<Error: 0 in Method UPDATEINT> - Sage 100 Business Object Interface - Sage 100 - Sage City Community