DOORS MDG Link creates <memo> field

[andrewd]

I have been mapping the DOORS requirements text to the EA “Notes” field without a problem.  I have found reasons why it’s better to map the DOORS requirements text to a tagged value instead.  However, I ran across a weird problem where about 5% of the requirements did not map the text and instead put the value <memo> in the tagged value field “Object Text”.  I have looked at the original requirements in DOORs.  The text is there in DOORS and I can’t see anything different between a requirement that did work and one that did not.  I am using version 12.0.1209

[smendonc]

It's likely that the 5% that didn't appear to map had text that was over 255 characters in length.  If memory serves anything up to 255 characters is stored directly in the tag value key value pair table.  Over 255 and the field gets mapped as a blob - can't remember where but hopefully this will get you started.

[Geert Bellekens]

Look into the notes of the tagged value. You'll find the contents there.

If that field is regularly over 255 characters you may want to choose to treat is as a memo field.

To do so go into the tagged values definitions (Project|Settings|UML Types...) and add

Code: [Select]

Type=Memo;
To the notes of the tagged value.

that will change the behavior of the tagged value and will always put the contents in the notes. It will also show a button [...] in the tagged value contents to edit the notes.

Geert