Bug using 'Property' as a field name

[Snow]

I think I've found a bug..... or at least a limitation in PowerApps. I work in commercial property so we use the word 'property' a lot! As an example, I'm building a system for one part of our business and I've labelled tables and fields using the word 'property' (probably not the best idea in retrospect). This wasn't a problem until I was trying to filter a list of items in a dropdown using the following statement:

Filter(Choices(SMR.LinkedSMR), Value in AddColumns(Filter(SMR,Property.Value = cmbProperty.Selected.Value),"Property Name",Title).Title)

The '=' throws the following error - "Invalid argument".
I've also tried the following variations.....

Filter(Choices(SMR.LinkedSMR), Value in AddColumns(Filter(SMR,SMR[@Property].Value = cmbProperty.Selected.Value),"Property Name",Title).Title)

and.....

Filter(Choices(SMR.LinkedSMR), Value in AddColumns(Filter(SMR,'Property'.Value = cmbProperty.Selected.Value),"Property Name",Title).Title)

Nothing seems to work. If I try to filter on another field there isn't a problem/error.
e.g.
Filter(Choices(SMR.LinkedSMR), Value in AddColumns(Filter(SMR,Department.Value = cmbDepartment.Selected.Value),"Property Name",Title).Title)

Any thoughts before I go through the large task of renaming the field?

[Mr-Dang-MSFT]

Formatted:

Filter(Choices(SMR.LinkedSMR), 
    Value in 
    AddColumns(
        Filter(SMR,
            Property.Value = cmbProperty.Selected.Value
        ),
    "Property Name",Title
    ).Title
)

If I'm understanding it,

• You're trying to filter down the choices of LinkedSMR in your SMR table.
• You only want the choices that match the Title of the same SMR table, but filtered down so that a lookup column for Property matches the value selected in the cmbProperty control.

How many Choices are there for LinkedSMR? If it's not that many and they are not subject to change, you can collect them.

Can you paste in the exact error you're seeing?

[Snow]

* You're trying to filter down the choices of LinkedSMR in your SMR table.

- Correct

* You only want the choices that match the Title of the same SMR table, but filtered down so that a lookup column for Property matches the value selected in the cmbProperty control.

- 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.

* How many Choices are there for LinkedSMR? If it's not that many and they are not subject to change, you can collect them.

- There could be a lot of choices for the LinkedSMR, hence why I'm trying to filter them.

I've attached a screenshot of the error and another similar error I've found when using a field called 'Property'.

Thanks for your help.

[Mr-Dang-MSFT]

Can you tell me more about 'Property'? What kind of column is it (maybe screenshot the list settings in SP)? Can you give some examples of its values?

[Snow]

It is a lookup field. See attached.

Example 'Title' values in the Property table/list:

Adlershofer Tor

Albert Einstein Ring

Bismarckallee 18-20

Bismarckstrasse

Eastgate

Eleven Office Center

Fangdiekstrassse

Fleethaus Schellerdamm

[Mr-Dang-MSFT · Accepted solution]

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. 

[Snow]

That totally makes sense now. I missed that logic. Thank you very much. Saved me a lot of work! Now I just have to worry about the delegation limitations.