How do I update Purchase Order Lines from the Purchase Orders form?

I'm modifying forms in the cloud and no access to the database.

I added SLPoitems as a secondary collection to the Purchase Orders form and then looping through the lines trying to update the due date. I can get the number of entries but unable to loop through and update.

Any ideas what I'm doing wrong or maybe I should be taking a different approach?

Thanks in advance.

Find more posts tagged with

Accepted answers

Richard Edwards

Thanks. I will give that a try.

All comments

ChuckAtDRI

I'd do it all in FormScript using LoadCollectionResponseData and UpdateCollectionResponseData objects, but the syntax for that is a little technical. In the old days I'd add a secondary collection, throw a hidden grid on the form, bind the secondary collection to it, then have an event handler to refresh the secondary collection and then call a form script to do the updating. The syntax for that is pretty simple.

dim oCol as IWSIDOCollection

oCol = ThisForm.Components("yoursecondarygridname").IDOCollection

For i as integer = 0 to oCol.GetNumEntries() -1

oCol.SetObjectPropertyPlusModifyRefresh("DueDate",i,<value>)

Next

oCol.Save()

Something along those lines.

Richard Edwards

Thanks. I will give that a try.

Richard Edwards

Thanks again for the example. The update doesn't save. Not getting any errors.

Richard Edwards

After tinkering some more, it works now. Thanks again or the example.

Tony Roper

What did you change to get it to work?

Richard Edwards

Think it was the refresh, not sure 😊.

Definitely had to refresh the secondary grid at the end of "StdObjectSelectCurrentCompleted" event.

Dim oCol As IWSIDOCollection

oCol = ThisForm.Components("<grid>").IDOCollection

For i as integer = 0 to oCol.GetNumEntries() - 1

oCol.SetObjectPropertyPlusModifyRefresh("DueDate", i, strDteTo)

Next
oCol.Save()

oCol.Refresh()

Richard Edwards

Oh, forgot to include in previous post.

Dim strDteTo As String = ThisForm.Components("<myDueDate>").Value()

Richard Edwards

A follow up question: How do I get the above to update the polines when more than one po were modified and then the save is clicked? It works fine if you're on the po working with a specific po.

ChuckAtDRI

I think you need to ditch the Secondary Collection and instead add a grid linked as a Sub-Collection. That takes care of the Save issue since saving a parent automatically saves its children. Also, if you leave it as a Secondary Collection you must save it before you navigate to a new Primary Collection record since a Secondary Collection is seen as a single collection of records and forcing it to refresh will prompt you to save or lose your changes. As a Sub-Collection you can navigate to other POs and it will keep the unsaved changes. At that point your coding is easier as well as you don't need to be manually saving and refreshing it. When you update the Sub-Collection it will also bubble up and mark the Primary Collection record as modified. The SetObjectPropertyPlusModifyRefresh takes care of that. Then you would do a normal save on the PO collection to commit all your changes to the Sub-Collection caches.

ChuckAtDRI

FYI for a simple example of a form with an editable Sub-Collection, look at the Chart of Accounts form and the Unit Code sub-collection grids.

Richard Edwards

Thanks.

Copyright © 2025 Infor. All rights reserved.