<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Multiple Property Values in Vault Forum</title>
    <link>https://forums.autodesk.com/t5/vault-forum/multiple-property-values/m-p/5600027#M43477</link>
    <description>Yes, ideastation candidate for sure. That data type is commonly called a "Multi-List" or in mySQL it is called an SET of ENUM values.&lt;BR /&gt;&lt;BR /&gt;For systems like MS-SQL, that don't have a data type for this kind of data, it can be stored as a delimited list of value ID's.&lt;BR /&gt;&lt;BR /&gt;Array would be a handy one as well sometimes, but in the end it really just ends up being a multi-level delimitted attribute.&lt;BR /&gt;&lt;BR /&gt;My company has some attributes that we hacked into multi-lists, but they are just text properties with semicolon delimited values in them (don't use commas, vault treats commas in text attributes really strangely.)</description>
    <pubDate>Mon, 20 Apr 2015 16:22:02 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-04-20T16:22:02Z</dc:date>
  </channel>
</rss>

