Ohhh that last screenshot explains everything--the field is a lookup to multiple values and not just one.
Filter(Choices(SMR.LinkedSMR),
Value in
AddColumns(
Filter(SMR,
Property.Value = cmbProperty.Selected.Value
),
"Property Name",Title
).Title
)
Here, Property can return many things, but cmbProperty.Selected.Value returns one which is why the condition does not work.
Likewise, ThisItem.Property.Value is not appearing in a label because it is not one thing. If you are expecting many things, you should use a control that can take a table: dropdown, combobox, gallery, etc.
Do you need the lookup field to look up multiple values? If not, I'd switch the checkbox for multiple values off.
@Snow wrote:- Actually, I want to list all of the Titles for the SMRs where the value of the 'Property' field in the SMR table matches the value in the cmbProperty control.
You'll definitely hit delegation limits here because you're evaluating a filter on a table for each of the choices in SMR.LinkedSMR. That's a lot of additional thinking.
Your logic would look something like this:
Filter(SMR,cmbProperty.Selected.Value in Property.Value)
This means, "Filter the SMRs where the value selected in the cmbProperty control is in the Property lookup field."
Note I reversed the condition since the single selected value could have membership in the Property field which can have many. Even though this logic kind of gets to what you're wanting, it's really not going to work out in PowerApps due to the delegation limitations with the connector.