Filter for Datacards within a form

[antonhh]

Hi there

I am in a bit of a pickle since nothing is working for me. What I have is a Form with several Datacards. What I want to do is to use 'Skill Category' to filter out 'Skill Name' for skills that have a matching skill category with.

For example If I pick for example "Power Platform" I only get 'Skill Name' for skills categorized by "Power Platform"

"Power Platform" Category should then filter Power Apps, Power Automate and Power BI

I have tried several things, and the closest I have gotten is under Item of SkillCard :  

Filter(
Choices([@'Skills Network'].'Skill Name'),
ThisItem.'Skill Category'.Value = DataCardValue1.Selected.Value
)

But I get an empty Choice field. What I have also tried is using Value in Filter like this:

Filter(
    Choices([@'Skills Network'].'Skill Name'),
    Value in Filter('Skills Network', 'Skill Category'.Value = SkillCategoryCard.Selected.Value).'Skill Name'
)

But get Error under Value in "Value in Filter"

Additional Information is I got a Sharepoint list with 'Skill Name' and 'Skill Category' as a lookup, they are two individual Lookup Columns if that is relevant.

[RandyHayes]

@antonhh 

Are your Lookup columns referencing records in another list that is the same list?  In other words, do the lookups lookup to two other lists or just one?

[antonhh]

Lookups are in two different lists yes. I did that since I had problem using the Category lookup to the 3rd list that contains all the Data.

The other two lists are fixed lists that I decided too divide up. Any advice for that decisions is very welcomed.

[RandyHayes]

@antonhh 

What problems did you encounter having it all in one list?

[antonhh]

There were absolutely no problem haveing skills and Category together as one list. My decision was based on when I am further down the line in this project to make it available for an administrator to add Categories and add skills to those Lists. As we are discussing this having Skills and Categories together in one List is maybe the better decision.

But that aside they Still will be looked up by Skills Network List.

[RandyHayes · Accepted solution]

@antonhh 

Yes, having in the same list in this case will save you some grief!

As for the Lookup...keep in mind that Lookup columns in SharePoint are "helpful" for the SharePoint interface.  They are not needed when connecting to your data via PowerApps (and preferred not to use in many cases) as it is more work for you to accommodate them.

A lookup column is a record.  It has an Id and a Value column.  The Id column is the ID of the record in the referencing list that the lookup refers to.  The Value column is the field in the referenced list that the lookup refers as its primary column.  Usually Title, but could be any other valid text field.  Check your list definition to ensure.

That all said, from the PowerApps perspective, you would not need to work with the Choices function in this case. You would simply work with the referenced list.

If you keep a Lookup column in your Skills Network list, then you would only need one if the lists are combined.  Your form as well would only need to have that one field in it.  

Now, having it down to one field. I'm going to call it Skill - as it will already reference a record in your CatsAndSkills list that has both the category and the skill in it.  So, there is no need for both.

Having both Category and Skill in the same referenced list, your Skill Category control would have an Items property of:

GroupBy(yourCatsAndSkillsList, 
    "Category", "_skills"
)

Your Skills control would have an Items property of:

yourCategoryControl.Selected._skills

Your Update property for the datacard would be (assuming you are still using a Lookup column):

With(yourSkillControl.Selected,
    {Id: ID, Value: Title}
)

(the above assumes Title as the connected column...adjust as needed)

[antonhh]

This seemed to do the trick for me.

Thank You @RandyHayes.