# Why does renaming the Archetype in a slot cause changing its cardinality?

**URL:** https://discourse.openehr.org/t/why-does-renaming-the-archetype-in-a-slot-cause-changing-its-cardinality/5702
**Category:** Template Designer
**Tags:** template
**Created:** [12 September 2024 06:43 UTC](https://discourse.openehr.org/t/why-does-renaming-the-archetype-in-a-slot-cause-changing-its-cardinality/5702 "2024-09-12T06:43:19Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![linforest](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/l/ac8455/32.png) [@linforest](https://discourse.openehr.org/u/linforest)
#### Post date: [12 September 2024 06:43 UTC](https://discourse.openehr.org/t/why-does-renaming-the-archetype-in-a-slot-cause-changing-its-cardinality/5702/1 "2024-09-12T06:43:19Z")

</div>

In Ocean Template Designer, why does renaming the Archetype in a slot cause automatically changing its cardinality from 0…\* to 0… 1?

For example, in the [openEHR-EHR-SECTION.immunisation\_list.v0](https://ckm.openehr.org/ckm/archetypes/1013.1.3727), [openEHR-EHR-ACTION.medication.v1](https://ckm.openehr.org/ckm/archetypes/1013.1.123) was dragged into the SLOT “Vaccinations administered”. When renaming the imported Archetype from “药物管理”(zh-CN; en: Medication management) to “预防接种条目” or any other names, its cardinality would be automatically changed from 0…\* to 0… 1. But I need its cardinality keep unchanged.

---

<div class="post-metadata">

### Author: ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)
#### Post date: [12 September 2024 07:56 UTC](https://discourse.openehr.org/t/why-does-renaming-the-archetype-in-a-slot-cause-changing-its-cardinality/5702/2 "2024-09-12T07:56:08Z")

</div>

Template Designer is following some older RM/AOM rules which insisted that a renamed slot had to be restricted in this way.

Since then the rule has been relaxed, so that the ‘no duplicate names’ rules is applied at run-time, not at design-time but TD has not been updated for some time AFAIK.

It was for us, one of the big benefits of moving to ArchetypeDesigner.

---

<div class="post-metadata">

### Author: ![linforest](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/l/ac8455/32.png) [@linforest](https://discourse.openehr.org/u/linforest)
#### Post date: [12 September 2024 08:07 UTC](https://discourse.openehr.org/t/why-does-renaming-the-archetype-in-a-slot-cause-changing-its-cardinality/5702/3 "2024-09-12T08:07:54Z")

</div>

If still sticking with the Ocean Template Designer, is there any workaround for this?  
Using a text editor, the cardinality could be manually restored to default (0…\*). But once it’s opened and saved again in the Ocean Template Designer, my effort will be in vain.
