# Ability not to link to end state entities

**URL:** <https://community.fibery.io/t/ability-not-to-link-to-end-state-entities/2729>\
**Category:** Ideas & Features\
**Created:** [April 21, 2022, 8:02am UTC](https://community.fibery.io/t/ability-not-to-link-to-end-state-entities/2729 "2022-04-21T08:02:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\
**Post date:** [May 2, 2022, 9:16pm UTC](https://community.fibery.io/t/ability-not-to-link-to-end-state-entities/2729/5 "2022-05-02T21:16:07Z")

</div>

Here’s a decent workaround, that might work for you.

Using Requests as an example you have your **Request** database and then you create an **Arch Request** database for archived Requests. When a Request is complete you [convert it](https://community.fibery.io/t/changelog-april-8-convert-entities-to-another-type-zendesk-integration-schema-changes-in-audit-log/1542#convert-entities-to-another-type-1) to an Arch Request and then delete the Request, this can also be handled by an automation.

Note that the Arch Request db should have all the same fields as the Request db and you will need to remember to update the Arch Request db when Request db fields are added or renamed.

---

_[View the full topic](https://community.fibery.io/t/ability-not-to-link-to-end-state-entities/2729)._