Current implementation of getReicprocallitems (Database Relationship) out of the box.

• Database 1 (Builds) links topics and display items in Database 2 (Items).

• Database 2 (Items) links topics back to Database 1 (Builds).

• Database 1 (Builds) does not display items from Database 2 (items).

Furthermore, having cross link records turned on and reading the description for it. It sounds like one-way street.

The way I try to use Database Relationship is:

• Database 1 (Builds)

  • Everyone can post topics

  • Linking topics from Database 2 (items)

  • Displaying said items from Database 2 (items) in Database 1 (builds).

• Database 2 (Items)

  • Only selected groups can post topic while everyone else read/view

  • Linking topics from Database 1 (builds)

  • Displaying said items from Database 1 (Builds) in Database 2 (items).

• While they both displaying items from each other, the styling of getReicprocallitems will be different since they will be using different database templates.

My suggestion and/or feedback of having database relations complete the cycle of displaying the items from the topic that it originally came from.

Now looking back; wow time flies. There was an issue that I brought up that got fixed; however I did mention there was another problem (not really) that I wished I had brought up. Detailing the full extent what I was trying to build and now I am back with this situation.

I use that feature a lot with all of its options, but I don’t understand what you are asking/recommending.

1. Database 1 (Builds) links topics and display items in Database 2 (Items).

2. Database 2 (Items) links topics back to Database 1 (Builds).

3. Database 1 (Builds) does not display items from Database 2 (items).

1) and 2) are the functionality of this feature. Being able to create a link within one record in one database and linking out to one or more records in a different database. The “cross link“ option allows to create a link back from the linked record to the linking records.
Line 3) does not make any sense to me.

My suggestion and/or feedback of having database relations complete the cycle of displaying the items from the topic that it originally came from.

What does “displaying“ mean in this context? The feature displays a link to the external record. Are you not seeing that? Or do you want to display another way, for example showing more than a link?

Also, are you using one database relationship field in one database or do you use that feature in both of your databases?

It’s unfortunately not clear and the labels Builds and Items don’t help, as we don’t know the context.

6 hours ago, opentype said:

What does “displaying“ mean in this context? The feature displays a link to the external record. Are you not seeing that? Or do you want to display another way, for example showing more than a link?

Also, are you using one database relationship field in one database or do you use that feature in both of your databases?

It’s unfortunately not clear and the labels Builds and Items don’t help, as we don’t know the context.

I want to show more than just a link from the database that I have database relationship on.

Database 1 is the hub where everyone will be posting in that has the database relationship on.

Database 2 is basically like a storage database.

When using a database relationship in database 1, I can pull any information from that onto database 2 but I wanted to do the opposite without needed a database relationship on database 2. I want to use a database relationship in database 1 to pull database 2 information; If that make sense.

I see.

It’s unlikely that IPS will change that behaviour, as there could be any number of fields with arbitrary content behind each link, like maps and YouTube videos and huge articles. If anything they could use the typical feed preview consisting of the title, a shortened body field and the record image. That would make sense and could be put into a nice grid view as alternative to the CSV list.

To customize the outgoing and incoming relationship fields, you would need some custom HTML. For the outgoing link that would go into the field settings (Display View Format) and for the incoming links it would be in the reciprocal links loop. All of that can be customized. I do that all the time.

Edited August 8, 2025Aug 8 by opentype

25 minutes ago, opentype said:

To customize the outgoing and incoming relationship fields, you would need some custom HTML. For the outgoing link that would go into the field settings (Display View Format) and for the incoming links it would be in the reciprocal links loop. All of that can be customized. I do that all the time.

So what I want to achieved isn't possible? Basically, all I wanted to pull is icon and image to display in database 1 without using a database relationship in database 2.

It requires custom PHP code in the field settings to replace the default link list with the code that pulls in the external record(s) with the fields you would like to display.

On 4.x it was easier, as there was a theme template for that, which one could customize. In 5.x that is not possible anymore, but the field settings still allow us to override the output of the database relationship field at least. That’s what I now use for some of my databases with database relationship fields.

Is it something you'll commission on? Would loved to get something like that.

Yes, I am available to set up Pages customizations like that.

https://opentype.space/support/75_custom-jobs/can-i-hire-you-for-custom-jobs-r36/