Hi William, looks like you’re right. However, there is a workaround here. If you go into the page XML, you can change the Conditions governing what data gets into your popup table for Child Accounts. If you click “View Page XML” for your page, you should be able to do a search for “popup” and find your Row Action popup’s XML. If you look inside it, you’ll find the XML for your Child Accounts table, which should have a child node, which looks like this:

<condition type="contextrow" field="Id" autocreated="true"/>

These “autocreated” conditions are the “smartness” that Skuid automatically puts in while you’re building popups. If you change the field=“Id” to be field=“ParentId”, then, as long as your accounts model has the ParentId field in it, your Child Accounts table in the popup should be filtered to just Child Accounts of the Account row in context.

Thanks but I can’t get this to work. Does the contextrow always take the primary key of the row to create the condition? I.e. in your example parentId = row.Id? In my case I want to use another field. Example: Show all other accounts from the same state.

you can specify the “primary key” field / merge field to dump in with the “mergefield” attribute, e.g.

<condition type="contextrow" mergefield="MailingState" field="BillingState" operator="="/>

Excellent! thanks