# Adding Lookup Keys to a List Lookup Definition from a Branch Life Cycle Could Override Some Prior Change(s) **URL:** \ **Category:** Nextworld Platform\ **Tags:** Feature-Request\ **Created:** [April 23, 2026, 2:43am UTC](https://community.nextw.com/t/adding-lookup-keys-to-a-list-lookup-definition-from-a-branch-life-cycle-could-override-some-prior-change-s/1979 "2026-04-23T02:43:28Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![david.lee](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/david.lee/32/331_2.png) [@david.lee](https://community.nextw.com/u/david.lee)\ **Post date:** [April 23, 2026, 2:43am UTC](https://community.nextw.com/t/adding-lookup-keys-to-a-list-lookup-definition-from-a-branch-life-cycle-could-override-some-prior-change-s/1979/1 "2026-04-23T02:43:28Z")
My colleague and I ran into an issue when adding a lookup key to a list lookup definition from our own branch life cycle. Both of us branched our own life cycles at the same time. Sometime later, my colleague added a lookup key to a list lookup definition and merged it to the base life cycle. After that, I could wipe out that change when I added another lookup key to the same list lookup definition and merged it to the base. Question: Why is there no way to either branch or check out a list lookup definition? That would prevent this kind of change conflict. ---
**Author:** ![ian.p](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/ian.p/32/427_2.png) [@ian.p](https://community.nextw.com/u/ian.p)\ **Post date:** [April 27, 2026, 7:14pm UTC](https://community.nextw.com/t/adding-lookup-keys-to-a-list-lookup-definition-from-a-branch-life-cycle-could-override-some-prior-change-s/1979/2 "2026-04-27T19:14:57Z")
The reason there is no way is it has never been supported. I am tagging this thread to the backlog idea for it.