I must be losing it.

[Mandu]

Invoices come in three flavors: "Sale", "Order", and "Staged". These are mutually exclusive, and the flavor is stored in Invoices::Flavor.

I want a layout that shows only Staged. So I create a self-relationship from Invoices to Invoices_Staged where Invoices::uc_Staged = Invoices_Staged::Flavor. uc_Staged is an unstored calc "Staged". Then I create a layout based on Invoices_Staged.

It's showing me all three flavors! Is my approach wrong?

Thanks very much.

Chap

[Fenton]

Creating a layout attached to the Invoices_Staged table occurrence (TO) is not going to restrict what records appear. A layout always shows the found set of the base table. The records are not "automatically filtered" by the TO. They would be filtered if you used Go To Related Record ( Invoices_Staged relationship; show only related, Invoices_Staged layout ) to get there.

I would think you would want a more flexible method however, as the above is going to show ALL Invoice_Staged records, whereas I'd think you'd want at the least a date range filter, or Find.

[Mandu]

I see my mistake -- I think. I should base the layout on Invoices, and use a portal to show Invoices_Staged.

That way it stays dynamic, updating itself as new records are flagged "Staged". Fortunately, I have no need for more flexibility in filtering at this point.

Thanks for clarifying the issue of layouts and base tables for me!