When I add an association between two records, GHL opens a drop-down that searches through all the records of the other object (attached screenshot). It's quick and prevents anyone from writing the name by hand. It works.

I ask to be able to use that same search engine as a custom field within an object or an opportunity. Today it lives only on the associations screen.

PROPOSAL

A new type of field, “Related Record”. When creating it, you choose the destination object and whether it admits one value or several. It is created just like a multiple-selection dropdown, and its values are records of another object.

As a field, it inherits what you already do with fields: it appears in forms and surveys, it merges into documents, emails and SMS, and the workflows read and write it like any other.

HOW WOULD THE FIELD WORK?

* It can be created both in custom objects and in opportunities.

* The field goes through the records of the destination object and provides them in the search engine in a multi-selection drop-down view.

* A filter can be added to the drop-down list that shows by a condition on the fields of the destination object, in the style of filters that already exist in the views.

For example: show the records of the custom object “materials” that meet the condition field status is “in use” and leave out those that are out of stock, removed or expired.

* automatic association. When you select one, the association is created automatically. If the custom field is in opportunity, and reference to the “Material” object, the opportunity-material association would be created

* Live at the level of a custom field, with everything that drags: being able to use it and print it in forms, merge it into documents and workflows.

EXAMPLE

Tattoo studio. Three objects: Session, Materials and Inks. Each session consumes different materials and inks, and the signed consent must list them. It's a health requirement, not a whim of reporting.

Session would have two multiple-selection fields, Materials Used and Inks Used, and the document would print:

Used materials: {{custom_objects.session.used_materials}}

Used inks: {{custom_objects.session.used_inks}}

Today the relationship can only be an association, and the document comes out empty: there is no way to go through the associated records in a template.

AT PRESENT

I ended up creating a private integration and an external service that reads the logs by API and rewrites the options of a drop-down. You have to issue a token with read and write permissions on objects, custom fields, opportunities and associations, and leave it alive on a server outside GHL. (2nd image)

It works and I keep it without problem. I write this suggestion because from the outside I sense that much of the work you have already done, even if I don't know the real implications of integrating it.

WHAT DOES IT UNLOCK

A workflow that reads a field with records inside can go through them and act on them:

* Inventory. Subtract stock when a session, order or visit consumes them, and mark out of stock when it reaches zero.

*Improved traceability through automatic associations.

* Measure consumption. Add up the amount spent on a job based on the records it has attached.

* Maintenance. Count uses of a tool and launch your review.

Each sector has its version, and they all end up in the same thing: interrelated objects and automations that need to cover that relationship.

Thank you for working with personalized objects this past year, the progress is very noticeable. This is the only piece that keeps forcing us to leave the product. Happy to give more detail or show the full case. Cheers to the team!