Why multiple portals?
You can set up your portal to show the entire log of status changes for the current order. You can specify a sort order for the portal so that the most recent status change is first in the list. You can specify a scroll bar for the portal if there might be more status changes logged than can be viewed at one time in your portal.
Won't that do what you need?
Thanks for helping. Your solution would work for a single order, unfortunatly i need to have an overview of multiple orders and their stausses. So Customer X has 4 orders, and i want to know wich of the 4 have a status of 10. Thats what i want to show in an portal.
I hope that it is possible, as it will give alot more clarity to the application that i am building..
You can set up relationships that use more than one pair of key fields. You can use this technique to set up one portal that "filters" for a specific status. You'd select a status from a drop down menu or a radio button list of status options and then only those would show in your portal. Or you could use the same basic trick to set up 4 different portals if you prefer.
Customer----<Orders---<Log (one customer can have many orders, One order can have many log entries).
Customer::CustomerID = Orders::CustomerID
Orders::orderID = Log::orderIDfk
Define a new field in Orders, (could be global), Status and make this relationship:
Orders::OrderID = LogByStatus::orderIDfk AND
Orders::Status = LogByStatus::Status
A portal based on LogByStatus (has some source table as Log) will only show log entries that match Status. For a filtered portal, you'd just select different values in the Orders::Status field.
For dedicated portals, you'd create one field in Orders for each status and link to separate table occurrences of Log.
Many folks find the terms Table and Table Occurrence confusing. To learn more, click the following link:
Table vs. Table Occurrence (Tutorial)