I have a layout based on a table called FabOps (build-records for hardware assemblies).
It is sometimes necessary to "transfer" a FabOp record to it's Next Higher Assembly (NHA). So I have a popover set up to allow the user to search for the NHA FabOp record, select it, then click a Submit button to execute it. The script basically stores the origin FabOp Record, the destination Fab Op record, date, who did it, etc. in a table called Transfers.
But I'm having trouble getting a portal to show ALL FabOps records when it's placed on a layout based on itself.
I tried a cartesian join on a self-relationship called "Fab_Ops_lookup" (Fab_Ops X Fab_Ops_lookup). I based the portal on the new relationship, but it shows the same record I'm on multiple times.
I thought cartesian would basically just show everything. But it's only showing the one.