OK I have it,



The problem is now if I change the supplier of a product the filter data is not updated… but this is not very important

duplicate the model for the products. Change the model type to aggregate. Group by the supplier name. Group by the ID. Apply this new model to your product table filter. Display the name. Provide the ID for the condition. just make sure that only your URL parameter is used in this new model.

yeah, I haven’t think that. But I think my final approach has the better perfomance.

Actually Pat has the canonical method for creating a filter on a string feild. Take a look at this document.  Look specifically at use case 6.  

Ok, I will try that way

I have a similar problem but a different use case. I want to put a condition on Model ‘A’ that the Id field is in the set of values of a field in Model ‘B’.

The issue is that (for heap purposes) I want to put a limit on Model ‘A’, the problem with that is that when I search on Model ‘B’ its limited to the results of what has loaded in Model ‘A’.

I tried using a subquery instead that uses the object of Model ‘A’, however, I cannot put any ‘dynamic’ data in Subcondition Logic. Either the Id parameter or a field from another model would do the trick but its reading it as plain text.

I’d help, but my head hurts already today. Can you take some screenshots or video. Not sure I could understand your use case from the text above.

Household is Model ‘A’ and CampaignMember is Model ‘B’.
Note: Since we are using Person Accounts, we put a custom Account__c field on CampaignMember

Oh. That subcondition logic is for when you have multiple subqueries. ie. (1 OR 2) AND 3.

Your next step is to create a subquery. That query will contain a condition for Field = CampaignID & Value is {{$Param.Id}}.



I mocked this up in one of my conditions. Just swap out:
- Quote_Component__c for CampaignMember
- Component__c for CampaignID

That was simple, I did not notice that add a sub-condition button. Thanks. It still doesn’t work for my case though because “The inner select field ‘Account__r.Primary_Household__c’ cannot have more than one level of relationships”