I'm building a solution for a parts catalog. The records in the main data entry table are called PageSets, which are created on a layout called DataEntry. A portal on the DataEntry layout lists the Parts for the particular PageSet. It does this by way of a match table, LineItems.

Related LineItems can be created in the DataEntry layout, within the portal. The key field for relating LineItems to PageSets is an auto-enter serial number in PageSets, PageSetID.

Often, when adding a new PageSet, its parts list is very similar to that of an existing PageSet record. So I go to the existing PageSet that I want to duplicate to use as a starting point, and then choose Records>DuplicateRecord. The record is duplicated and its auto-enter serial number is created. But the portal is empty, because I have not yet created any LineItems related to the new PageSetID number.

I would like to be able to Duplicate Record, and have the newly created record also create duplicates of the related LineItems, but related to the new PageSet ID. I could then modify the fields of the LineItems in the portal (quantity, etc.) and be done with the new PageSet without having to key in part numbers all over again.

Will I need to use a script to do this? Before pursuing that, I just want to make sure there is no way to tell the DuplicateRecord command to also duplicate related records shown in a portal.

Thanks!

James

Will I need to use a script to do this? Before pursuing that, I just want to make sure there is no way to tell the DuplicateRecord command to also duplicate related records shown in a portal.

You will!! Take a look at the attached template, however is there one aspect to consider, older orders might have bygone prices, so you might to think of relookup when each line is duped! This is what I suggests in the script listing above!

--sd

Orders.zip