Hi Hans,
I apologize for the delay, as I'm not sure how this ticket remained unattended for this long.
What you're planning is possible using the shortcode attributes passed through the view's shortcode.
Here is an example:
1. Suppose you have a view named 'view-to-show-books', that shows all books posts. Its shortcode would like this:
( ref: https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-view )
[wpv-view name="view-to-show-books"]
2. To filter the view, based on the value of the custom field with slug 'book-type', you can include a query filter, that looks for the field's value passed through the shortcode attribute 'type'.
( example screenshot: hidden link )
3. After that, you'll be able to use this same view to show different book post results, by changing the custom field value, in the shortcode attribute:
For example, to show only the books where the 'book-type' field value is 'one', the view's shortcode will be:
[wpv-view name="view-to-show-books" type="one"]
And for the books where the 'book-type' field value is 'two', the shortcode will be:
[wpv-view name="view-to-show-books" type="two"]
This way, you won't have to create separate content templates and the results from the same view can be changed, by just changing the shortcode attribute value in the view's shortcode.
I hope this helps and please let me know if you need any further assistance around this.
regards,
Waqar