Yes, this is expected behavior (assuming your value list is set to fetch "all values").
I'm not sure what you mean by "just the record browsing" (would that be just one value?). However, the basic method for filtering a value list is to create a relationship to the target table and use "related values" in the value list setup.
Maybe if you describe in more detail what you're trying to do, we can offer more specific advice.
What I am trying to achieve is a dynamic drop-down of Symptom codes for a product. Say I have 10 records, each of them contain a different serial number. The serial number is sent off to a 3rd party API which returns a different list of Symptom codes based on the serial number. Symptom codes are placed into a hidden field which autocalulates the value to switch it from the Pipe separated list to a Value list, This is all working as expected. Its just the behavior above that I had issues with, I only want the drop down to show values that relate to its serial number not all serial numbers.
I think your correct that I will need to create a "Self Join" relationship and grab the values from the 2nd database. I will give this a go now. Thank you Mike.