# Template Designer problem when selecting Value Set on DV\_TEXT node

**URL:** https://discourse.openehr.org/t/template-designer-problem-when-selecting-value-set-on-dv-text-node/15651
**Category:** Technical (archive)
**Created:** [25 July 2015 03:41 UTC](https://discourse.openehr.org/t/template-designer-problem-when-selecting-value-set-on-dv-text-node/15651 "2015-07-25T03:41:26Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![pablo](https://discourse.openehr.org/user_avatar/discourse.openehr.org/pablo/32/3505_2.png) [@pablo](https://discourse.openehr.org/u/pablo)
#### Post date: [25 July 2015 03:41 UTC](https://discourse.openehr.org/t/template-designer-problem-when-selecting-value-set-on-dv-text-node/15651/1 "2015-07-25T03:41:26Z")

</div>

Hi,

I have a text node and was testing different ways of constraining that node from the Template Designer.

I’ve found that if I select the node, then on the node properties panel go to: Value Set \> On the window, under the “Terminology Service” tab, select “Snomed” and check the “Select full terminology”, then save the OET. That constraint doesn’t appear in the OET file.

If I go to the “Generic Valueset” tab on the same window, and input a Terminology Name and a Subset name, then save the OET, that constraint appears in the OET. Also, the node type changes from DV\_TEXT to DV\_CODED\_TEXT, something I reported in other issue that I couldn’t set the constraint on DV\_TEXT to allow only DV\_CODED\_TEXT instances. So setting the Generic Valueset seems to be an implicit way of declaring that node as DV\_CODED\_TEXT from the TD.