Problem:

The issue here is that the user wanted to restrict their relationship forms relationship fields to only the posts that the user created.

Solution:
There is an option on the relationship form fields that allows you to only pull the options for the current user. What this means is that they will only see a list of options that they are the authors for.

Under the filtering option you should be able to set it to get only the current user's posts.

Problem:
pass value of a post:custom field thru to next page as a hidden parameter

Solution:
Toolset uses the WordPress standard to store the custom fields. The custom post type custom fields will be saved to postmeta table.

You will have to check how you can get the custom field value either using the get_post_meta() function but to get the custom field value you will require the post ID. You have to find how you will pass the post ID so that based on the passed post ID you can get any custom field value using get_post_meta() function based on the passed post ID.

Relevant Documentation:

Problem:

Display Woocommerce order customer's billing fields.

Solution:

For those Woocommerce order placed by logged-in user, you can use below codes to output billing company field value:

[wpv-conditional if="([wpv-post-field name="_customer_user"] eq 0)" evaluate="false"][wpv-user field='billing_company' id='[wpv-post-field name="_customer_user"]'][/wpv-conditional]

For guest user(none-logged-in), you can use below codes to output billing company field value:

[wpv-conditional if="([wpv-post-field name="_customer_user"] eq 0)" evaluate="true"][wpv-post-field name="_billing_company"][/wpv-conditional]

Relevant Documentation:

Problem:

After playing around with many new views and creating the template for the output/results/loop, and then deleting these new views, I find I am left with loop templates that no longer are attached to the views because the view has been deleted. Is there any way I can clean up the loop templates?

Solution:

You can trash/delete the post views, then all content templates in the view's loop will be removed too.

Relevant Documentation:

Problem:

Should I always create the Content Template first, then various View(s) to place the Content Template shortcode, and afterward add Content Template(s) into a View(s)?

Solution:

If the content template will be used in only one post view, you can create the post view first, and generate the content template automatically.

If the content template will be used in multiple cases, then you can create the content template first, and display the content template shortcode in where you want, for example

[wpv-post-body view_template="my-ct"]

Relevant Documentation:

https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-post-body