I'm wondering if it possible to make a dropdown value list with related values from a table from another file?
Both files are on the same server.
I can't seem to get it to work.
Yes it is possible and depending on what you need to appear in the value list, you might not need a relationship.
You'll need to tell us what you've tried that doesn't work before we can assist you in much detail. Accessing data from another file requires a working external data source so that's probably the first point of failure here.
You mention "related table".
Do you have a table occurrence of the other-file table on your current file's relationship graph?
If not, you can add one by adding an external data source, selecting that file and adding an occurrence into your current file.
Set up your relationship as necessary and then, like normal, create a value list.
Let me try to explain.
I have a file called Ingremate in which table A_001_Artigos 2 is joined (table A_002_Fornecedores_artigos) to table B_001_Contatos).
In another file I have a Layout based on table A_002_UniversalDocument. On that same table I have the foreign key from table B_001_Contatos 4 (occurence from file Ingremate). On that same layout I have a portal showing records from table A_001_Quantity 2.
On this portal I created a field A_001_Quantity 2::A_001_Artigos_IdFk which is a pop-up menu and has value list which uses values form A_001_Artigos 2. This works and shows all records from A_001_Artigos 2. I would ilke this valuelist to include only related values from A_002_UniversalDocument::ContacosIdFk. In this what I can't get to work.
Thanks all for your time.
The fact that some of this data is from a different file does not appear to be a factor here.
What you need is a valid relationship that is "downstream" from your portal's Table Occurrence. (We call a "box" on your relationship graph a "Table occurrence" to differentiate them from the data source tables to which they refer.)
Make a copy of the A_002 table occurrence. Link it as needed to your portal's Table Occurrence (A_001). Set up your value list to list values from this new occurrence of A_002 and you should then be able to set it up to use the "include only related value" option.
However, this does not make much sense to do this. The relationship from A_002 to A_001 is one to many. Thus the "many to one" relationship that I have just described would only produce a value list of a single value.
Retrieving data ...