It actually works the same. But with a portal, you are dealing with two table occurrences--the TO for the layout and the TO for the portal. From what you describe it sounds like you have specified the layout's TO as the "starting from" setting in value list set up instead of the portal's TO.
When I choose the portal's relationship as the starting from, the filtering in the first field stops working. The portal is just based on a value of a global to give a first filtering. Then we create portal rows and as we fill date in the row, the lists should be conditional based on the entered data. That is a given.
By the way. I am trying to get data not in the table of the portal but in another table related to the portal table. So, I need to make the same relationship to another table work in the portal that occurs in the actual table.
You'll need to describe your set up in detail. How is your layout designed? What tables/relationships are involved? How exactly did you set up the value list in Manage | Value List?
I just want to get a vendor's items from a Price table in an Order table view.
From the Order table, the conditional value list of the vendor's items is a snap, no worries.
However, I create a portal view of the Order filtering just current (pending) orders based on a global, easy.
Then I just want to do the same thing again. Get the items for a vendor in a portal row from the Prices table.
This is funny, I have been using FM for 20 years, you think this would be easy. :)
You have to choose the actual Order table as the starting point for the conditional value list to work in the portal. You do not choose the relationship that creates the portal as the starting point.
Thank you Phil.