# \[✔︎ FIXED\] Can't create a specific relation **URL:** \ **Category:** Bugs & Issues\ **Created:** [April 16, 2019, 9:57am UTC](https://community.fibery.io/t/fixed-cant-create-a-specific-relation/204 "2019-04-16T09:57:56Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Shafqat\_Ullah](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/shafqat_ullah/32/101_2.png) [@Shafqat\_Ullah](https://community.fibery.io/u/Shafqat_Ullah)\ **Post date:** [April 16, 2019, 9:57am UTC](https://community.fibery.io/t/fixed-cant-create-a-specific-relation/204/1 "2019-04-16T09:57:56Z")
Hi, 1. I had the following structure: Product → Capability. 2. I had to introduce another level named “Capability Area” in the middle so that the structure becomes: Product → Capability Area → Capability. In order to do that, I renamed the existing “Capability” type to “Capability Area”. 3. Then I added a new type named Capability under Capability Area, thereby achieving Product → Capability Area → Capability. 4. For a productive board view to manipulate the relations, I need the Capabilities as cards, Products as columns and Capability Areas as rows. For this, I need a relationship from Product to Capabilities directly, too\*. But the problem is now I can’t create a simple relation from Product to Capability entity or vice versa as seen in the screenshot below: ![31%20pm](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9d102c2ec96a4d790981ded3d078fd043466b14e.jpeg) I have a hunch that this is being caused due to the system getting confused because of the old “Capability” type that was later renamed to “Capability Area” - I had seen such stale type names in the exported JSON in general (but didn’t analyze further for this case). \*BTW, this is an example where “Extended or Derived” relationship concept could otherwise help and not require explicit relations beween all levels in a relationship hierarchy or chain. ---
**Author:** ![Shafqat\_Ullah](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/shafqat_ullah/32/101_2.png) [@Shafqat\_Ullah](https://community.fibery.io/u/Shafqat_Ullah)\ **Post date:** [April 16, 2019, 10:52am UTC](https://community.fibery.io/t/fixed-cant-create-a-specific-relation/204/2 "2019-04-16T10:52:58Z")
Yup! Must be the stale type name references! I just renamed the “Capability” to “Product Capability” and now the relation can be created without any error message. The underlying bug should be fixed asap - otherwise exports won’t work correctly and such type renaming is a common need. ---
**Author:** ![Shafqat\_Ullah](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/shafqat_ullah/32/101_2.png) [@Shafqat\_Ullah](https://community.fibery.io/u/Shafqat_Ullah)\ **Post date:** [April 16, 2019, 11:26am UTC](https://community.fibery.io/t/fixed-cant-create-a-specific-relation/204/3 "2019-04-16T11:26:43Z")
I think the following bug is related to this bug: > [@Exported JSON has references to old Type names](https://community.fibery.io/t/exported-json-has-references-to-old-type-names/162): > > Hi, The exported JSON has references to old Type names which had been renamed. There may be other such stale data. Thanks! Shafqat ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 1, 2019, 3:45pm UTC](https://community.fibery.io/t/fixed-cant-create-a-specific-relation/204/4 "2019-08-01T15:45:01Z")
Fixed in latest build ---
**Author:** ![Shafqat\_Ullah](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/shafqat_ullah/32/101_2.png) [@Shafqat\_Ullah](https://community.fibery.io/u/Shafqat_Ullah)\ **Post date:** [August 3, 2019, 6:25am UTC](https://community.fibery.io/t/fixed-cant-create-a-specific-relation/204/5 "2019-08-03T06:25:54Z")
Thanks @mdubakov!