# Feature - Custom field type of "thirdparty" reference

**URL:** https://discussions.eramba.org/t/feature-custom-field-type-of-thirdparty-reference/1498
**Category:** Forum - Software
**Created:** [April 11, 2020, 12:07am UTC](https://discussions.eramba.org/t/feature-custom-field-type-of-thirdparty-reference/1498 "2020-04-11T00:07:40Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![barry.kaplan](https://discussions.eramba.org/user_avatar/discussions.eramba.org/barry.kaplan/32/1378_2.png) [@barry.kaplan](https://discussions.eramba.org/u/barry.kaplan)
#### Post date: [April 11, 2020, 12:07am UTC](https://discussions.eramba.org/t/feature-custom-field-type-of-thirdparty-reference/1498/1 "2020-04-11T00:07:40Z")

</div>

Following the model of asset wrt thirdparty as discussed in [Question - SaaS Applications - Assets, Third Parties, or Both?](https://discussions.eramba.org/t/question-saas-applications-assets-third-parties-or-both/472)

That model works good. But there is no clean to associated the SaaS asset the Supplier thirdparty that hosts/provides the SaaS. I thought I would just create a custom field to refer the thirdparty, but custom field values are all static.

A general enhancement would be to support a custom field type that provides a lookup to entities. When rendering in a report or editing, it should be possible to navigate to the related entity.

Sure, it would be great if the relationship could be bi-direction. But I’m expecting, even this feature is implemented, that bi-direction would much more complex.

---

<div class="post-metadata">

### Author: ![m.rossi](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/m/d26b3c/32.png) [@m.rossi](https://discussions.eramba.org/u/m.rossi)
#### Post date: [July 21, 2023, 7:55am UTC](https://discussions.eramba.org/t/feature-custom-field-type-of-thirdparty-reference/1498/2 "2023-07-21T07:55:24Z")

</div>

I would also like to ask for this feature.
