That would display the nested View and pass the current post ID from View 1 into an attribute attr1, and it would pass the value of custom field some-slug from the current post of View 1 into an attribute attr2.
Then in View #2, you can set various Query Filters to respond to these shortcode attributes, or you can use the wpv-attribute shortcode to access those attributes in the Loop editor:
Parent post ID: [wpv-attribute name="attr1"]<br />
Parent post custom field "some-slug": [wpv-attribute name="attr2"]
Problem: I have a nested View structure that shows parent posts in the outer View and child posts in the nested View. In some cases the parent post has no child posts, and I would like to hide those parent posts in the results. The problem is that the nested child post View is filtered. Is there a conditional that tests whether or not a parent post contains these filtered child posts?
Solution: You can solve this without custom code by restructuring the Views. Instead of displaying the parent post information in the outer View, display the parent post information in the nested child View, inside wpv-items-found but outside wpv-loop. Use the item attribute to display parent post information with any shortcodes in the nested View, since the post context in the nested View is the context of the child posts. The syntax for the item attribute is item="@relationship-slug.parent" in a typical one-to-many (O2M) relationship.
