Hi everybody!

Could you please look at free FileMaker Solution Framework <<ftp://ftp.apple.com/filemaker/solutions/FileMaker_Solution_Framework.sit>>

There you are the Invoices (portal with Quantity, Price, Amount, etc.) and the Products (Price, Default Order Quantity, etc.), and a join file LineItems.

The Product information is called into the portal at the Invoices db layout by a script ("Choose Product") attached to a button "Add item" :

PerformScript [sub-scripts, "[RTN] = "Save Portal Row""]

Set Field ["PRODUCT_Constant::_Variables", "InvoiceNumber"]

Set Field ["PRODUCT_Constant::_ButtonControl", ""AddItem""]

PerformScript [sub-scripts, External: "Products.FP5"]

PerformScript [sub-scripts, External: "Products.FP5"]

with a routine sub-script [RTN] = "Save Portal Row" :

If ["Status(CurrentPortalRow) = 0"]

Go to Portal Row [select, Last]

Set Field ["_PortalID", "Status(CurrentPortalRow)"]

Else

Set Field ["_PortalID", "Status(CurrentPortalRow)"]

End if

Suppose, at the Invoice layout I need the second, almost identical portal (portal2) of the same operational mode, joint through the second LineItems2 file to the same Product db (to complete a kind of manufacturing solution). Careful copying, renaming (portal, button, scripts, field names, relationships - anything), etc. result in a disaser: not only the second portal is unavailable, but also the original one shows the first row only. Removing the second portal restores the functionality of the first one. The problem is the absence of a portal address. How to push the data into the required portal ? How to set an address or to name it ?

Thank you for your thoughts

Add Go To Field [relName::fieldName] step before Go To Portal Row step, where relName::fieldName define the portal (relationship)

Dj

Dear Dj,

It is not so easy, unfortunately...

The actual setup is very intelligent, rather complex, and involves a number of global fields difficult to handle. At least, I can't succeed yet. Are You? Or it is just a common sense suggestion?

Regards

Dear Dj,

You are absolutely right. Actually, the problem was due to an orphan field of the same name as in LineItems db (in a modified set)

Thank you very much, Master.