Okay thank you for the additional information. I can think of two ways to accomplish the display you have described, filtered by date:
1. Instead of storing the Tour Start Date information in a date field that supports multiple values, add a new repeatable field group (RFG) to the Cycling Tour field group and place a date field in this RFG. When you edit a Product (Tour), add a new row to the RFG for each tour start date.
Instead of a View of Products (Tours) to display these tours and dates, create a View of the RFG. Now it is no longer necessary to use a wpv-for-each shortcode, because each date field only contains a single value. In the loop of the RFG View, insert the date custom field value using a Types field shortcode. To display information about the parent post, like the parent post title and the parent post duration field, use the item attribute with @relationship-slug.role syntax:
[wpv-post-link item="@rfg-slug.parent"]
[types field="tour-days" item="@rfg-slug.parent"][/types]
Replace rfg-slug with the slug of the new dates RFG.
This solution requires no additional custom code, but it has limitations. The main limitation is that a View of RFGs cannot be filtered or sorted by fields in the parent post type, and a View of the parent post type cannot be filtered or sorted by fields in the RFG. This might be a problem if you plan to add Query Filters to the results here based on fields in the Product (Tour) post. For example, if you plan to filter the results by price, accommodation, fly out of, etc., this will require custom programming.
If you are already displaying the Tour Start Date fields in a View, template or other location on the site, you'll need to update that code to display the new date field. Usually a View is required to display information like this from an RFG.
2. Create a custom solution using our PHP APIs. I can help you find the relevant documentation for these APIs, I can share code examples, and I can help troubleshoot your code if you run into problems. However, I cannot create a copy + paste custom solution for you per our support policy: https://toolset.com/toolset-support-policy/
This solution is the most flexible, but it requires developer-level understanding of PHP, WordPress, and Toolset APIs.
Let me know if you have questions about these two options, or let me know how you would like to proceed.
