Confirm Constraint Logic for Nested SFDC Custom Objects

[Kim_Wieczner]

We have re-architected the way our client subscriptions pull into Salesforce, and the detail we need is on Account>Subscription>Subscription Product & Charges.

I've been able to bring in the necessary fields for that object into Marketo but they're only available as constraints on the subscription so "subscriptions with product & charge: field name." Subscription to Subscription Product & Charge is a 1: many relationship. My concern is that putting constraints like the below would not necessarily query the SAME product & charge line:

So it could look for one that is active but that might not be the one I'm looking for.

Can someone help confirm and/or point me in the direction of an alternative?

Thanks,
Kim

[SanfordWhiteman · Accepted solution]

The “with” constraints on the junction object always pertain to the same junction object record.

[Cristian_Nanan]

I'm working on something similar at the moment and it doesn't query the same product & charge line. So if you have a subscription with a child product & charge Active = FALSE but Name is a match, and another child product & charge Active = TRUE but Name is not a match, this filter will pull it in as the constraints are technically satisfied (across different child records).