ACF 6.2: Built-In Bidirectional Relationship Fields and Option Pages

Coming in ACF 6.2 are two new features, built-in bidirectional relationship fields and built-in option pages. Relationship fields let you connect two post types together and a bidirectional field means when you update one Custom Post Type, the other one is updated with the change also. Option pages in the WordPress admin allow you to create site-wide variables. Up until now these features required a code snippet to enable, but with ACF 6.2 they can be setup with the user interface.
There is a text summary of the article on the WebTNG website: www.webtng.com...

[@DesignwithCracka]

It’s good to see ACF getting these updates. Thanks for the video!

[@MainsailWebDesign]

You saved me hours of troubleshooting time. Thanks! I hope you make more videos about ACF

[@maxziebell4013]

Neat… I also used snippets for option pages on a regular basis. I probably won't go back and remove them, but going forward, this is convenient!

[@njordhoder]

Great video. Well prepared and explained. Thanks David!

[@DavidMcCan]

Glad you liked it. Thank you.

[@KshitijShah89]

This was a great explanation thanks!

[@mohammadmahdialvansaz8001]

thank you very much

[@mightylotan]

Hi David McCan, thank you for this tutorial. I was wondering, how do we display information from the field in a relationship? For example, in your Book Author CPT, you have a relationship field with books; how could we make a list of books that includes data about the book (set in the Book CPT) such as publish date, genre?

[@hosseinkhanmohammadi4770]

Thank you.

[@peteharrison3241]

I realise this is some what out of date now as this functionality is fully released, but I have a related question to do with Relationships and the new Bi-Relationship type.
I see so many tutorials about relationships, and most create a third field group, the way you might do if creating a many-to-many relationship in MySQL, and your's is the only one that uses the relationship directly between the two field groups, I wonder if you have any thoughts on why people might do it that way vs the way you've shown here?

[@MarcoPrincipia]

Thanks for this! Very clear. First time I've fully understood how the bidirectional relationship field works. One question: how can one "force" this relation to build up if the two CPTs and the field already existed but it wasn't set properly?
I mean: is there a way to force the "Audio Books" to read their related "Book Author"? Or it should be done manually one by one?

[@DavidMcCan]

It is possible if you are using a plugin to display the related content that you can set a condition, but I've always gone record by record to set the relationship.

[@ksncreativestudio]

NIce!

[@AaronJamesKeyes]

I have a question. This helped me setup the BDR correctly, so thank you. However, how do you bring in the content once it's set up. In other words, if you were to view an author's single post page, how do you get their books to show up like you would for related posts, for example. Styled with an image, title, description, etc. and link to that book's single post page. Please help.

[@DavidMcCan]

You use a tool that supports ACF relationships. Here is a video where I showing doing just that with Cwicly. th-cam.com/video/rEwNbzlM8J0/w-d-xo.html

[@Xboxers]

Did they change anything in the way relations are saved in the database? Compared to Metabox they weren't having the best relational performance.

[@DavidMcCan]

No. If you are talking about using custom tables then there is a plugin from hookturn for this for ACF, Meta Box has it in their premium, JetEngine and Pods have it too. Note that it may require extra programming for displaying the values as most tools use the default post meta option.