Publication::idiom = "English" // the exact spelling
Publication::idiom ≠ "English"
You could also create a global text field and format it with the same idiom value list, then use that field instead of the hardcoded value.
For this I create a global field such as glb_Idiom. That's the field you'd put on the screen and associate it with the value list you mentioned. The portal would be based upon a relationship that uses that global field in addition to whatever else you wish to base the relationship on, such as:
PrimaryKeyID = ForeignKeyID
glb_Idiom = Idiom
Thanks a lot for your help! It almost worked.
I still have a question: when I change the idiom from English to any other idiom the portal records doesn't update. I have to close the file an reopen it to get portals updated.
Any idea how to refresh it?
If you have 14 or 15, try a trigger with
Refresh Portal [ "yourPortalObjectName" ]
or set the layout table relationship key to itself; that will re-evaluate the relationship and any filters.
If all else fails, use Refresh Window [ flush cached join data ]
It worked with the last sugestion you made, but that is useful for me because I have more than one portal per layout, this way I don't need to replicate Refresh Portal.
You made my day twice!!!
Thanks for your suggestion! I was already trying Erolst suggestion and it di work.