# Cockpit CMS V1 - Collection-Link to Latest Version

**URL:** <https://discourse.getcockpit.com/t/cockpit-cms-v1-collection-link-to-latest-version/2970>\
**Category:** Uncategorized\
**Created:** [May 3, 2024, 11:19pm UTC](https://discourse.getcockpit.com/t/cockpit-cms-v1-collection-link-to-latest-version/2970 "2024-05-03T23:19:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![COValhalla](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/covalhalla/32/1295_2.png) [@COValhalla](https://discourse.getcockpit.com/u/COValhalla)\
**Post date:** [May 3, 2024, 11:19pm UTC](https://discourse.getcockpit.com/t/cockpit-cms-v1-collection-link-to-latest-version/2970/1 "2024-05-03T23:19:00Z")

</div>

Hello,

I’m on Cockpit CMS V1 still and wondering if there is an easy way to fix an issue I’m having with Collection-Links. For example, I am linking from an Order to a Part Type. If I edit the Part Type directly, the link still goes to the old version.

Is there a way to have the linked item always reference the latest version of it? Other than a built in solution, I’d probably have a crontab run nightly to update all links to the latest, but that seems janky.

Thanks

---

<div class="post-metadata">

**Author:** ![joe09](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/joe09/32/1451_2.png) [@joe09](https://discourse.getcockpit.com/u/joe09)\
**Post date:** [June 27, 2024, 5:12am UTC](https://discourse.getcockpit.com/t/cockpit-cms-v1-collection-link-to-latest-version/2970/2 "2024-06-27T05:12:35Z")

</div>

You can address this issue in Cockpit CMS V1 by using dynamic queries or hooks to ensure links always reference the latest version of a linked item. This approach avoids the need for a nightly crontab job.