Table: Items

Contains all Vault Item Master records – each representing a specific Item version, including metadata such as revision, category, lifecycle state, creator information, and user-defined properties.

Columns

Column	Data Type	Can Import	Allows Null	Default	Description
🔑ItemNumber	nvarchar(128)	✅ Required	❌		Unique Vault Item Number, that remains the same across all versions.
Category	nvarchar(50)	✅	✅		To be filled with a valid Vault Item category. If null, DTU applies the default category.
Revision	nvarchar(20)	✅	✅		Revision label. The values must fit to the target Vault’s Revision Scheme Definition.
RevisionDefinition	nvarchar(100)	✅	✅		To be filled with a valid Vault Revision Scheme Definition, that is defined in the target Vault. If null, DTU assigns the default scheme.
🔑Version	int	✅	❌	1	Sequential version number, starting with 1 for each Item.
Title	nvarchar(500)	✅	✅		Fills Vault system property Title (Item, CO). In the Vault Client, only a maximum of 128 characters can be entered.
Description	nvarchar(1000)	✅	✅		Detailed description. Fills Vault system property Description.
Unit	nvarchar(20)	✅	✅		Fills Vault system property Units. If null, Vault defaults to ‘Each’.
LifecycleState	nvarchar(50)	✅	✅		To be filled with a valid Vault Lifecycle State, if allowed by the Category. If null, DTU assigns the default state.
LifecycleDefinition	nvarchar(100)	✅	✅		To be filled with a valid Vault Lifecycle Definition, if allowed by the Category. If null, Vault assigns the default lifecycle.
CreateUser	nvarchar(100)	✅ Required	✅		The Vault user who created the Item version. Fills Vault system property Originator. Must exist in the target Vault; otherwise DTU skips the item during import.
CreateDate	datetime2	✅	✅		The date the version was created. Fills the Vault system property Original Create Created. If not specified, Vault displays the current date.
Comment	nvarchar(1000)	✅	✅		Optional version note. Fills Vault system property Comment.
UDP_…	nvarchar(max)	✅	✅		Columns starting with UDP_ define user-defined properties in Vault. They can be added as needed. Note: ‘UDP_Equivalence Value’ is required to assign the PartNumber. For a complete import of status, category, and revision data on historical versions, DTU may also require additional system properties: UDP_... (Historical).
_OriginalBCPOverflow	xml	⚪ auto (only available when importing from a source Vault BCP package)	✅		Enables identical re-export of the BCP package. Stores additional XML data from the original BCP file that is not captured by other columns (e.g. attributes like ItemNumberID=,IsReleased=, IsObsolete=, BOMStructure=, PartNumber= or nodes like historical <ItemNumber, the <Effectivity, <itemRefDesMaster, <Detail).

Remarks

Each Vault Item version is uniquely identified by the combination of ItemNumber and Version.
These columns together form primary key of this table.

When transferring multiple Item versions, the Category, but also Revision, and RevisionDefinition are stored redundantly for each Item Version.
Changes to these attributes should therefore always be applied to all versions (or all versions belonging to the same revision).

Handling System Properties for DTU Imports

DTU does not automatically assign the Vault system properties “Released” and “Obsolete” based on the LifecycleState of the Item version.
For imports from BCP packages, this information is stored in the _OriginalBCPOverflow column (IsReleased= and IsObsolete=).
Therefore, for newly inserted item records, these system properties may be incorrect in the target Vault.

After DTU imports from several BCP packages, the following system properties may be empty in Vault:

• Category Name (Historical)

• Lifecycle Definition (Historical)

• State (Historical)

• Revision Scheme (Historical)

If the BCP package includes these date, the Items table will have corresponding UDP_....(Historical) columns. If these columns are missing, they should be created.
To ensure that changes to LifecycleState, LifecycleDefinition, Category, and RevisionDefinition are correctly reflected in the target Vault, these UDP_...(Historical) columns must also be updated or populated properly (see example below).

Examples

Retrieving all versions of a specific Vault Item, including their metadata

SELECT ItemNumber, Category, Revision, RevisionDefinition, Version, Title, Description, Unit, LifecycleState, LifecycleDefinition, CreateUser, CreateDate, Comment, UDP_Equivalence Value, UDP_F360M Link
FROM Items
WHERE ItemNumber = '100005'
ORDER BY Version;

ItemNumber  Category Revision  RevisionDefinition          Version Title                 Description                   Unit  LifecycleState    LifecycleDefinition   CreateUser  CreateDate           Comment              UDP_Equivalence Value UDP_F360M Link
----------- -------- --------- --------------------------- ------- --------------------- ----------------------------- ---- ------------------ --------------------- ----------- -------------------- -------------------- --------------------- ----------------------------------------
100005      General  A         Standard Alphabetic Format  1       Bottom - Front        First prototype.              Each  Work In Progress  Item Release Process  Hannes      2024-01-12 09:40:00  Initial creation.    100005                https://mycompany.autodeskplm360.net/...
100005      Part     A.1.1     Standard Alphabetic Format  2       Bottom - Front        Minor geometry updates.       Gram  Released          Item Release Process  Albert      2024-03-04 14:15:00  Revised CAD model.   100005                https://mycompany.autodeskplm360.net/...
100005      Part     B         Standard Alphabetic Format  3       Bottom Plate - Front  Added new vendor references.  Gram  Work In Progress  Item Release Process  Jane Doe    2024-06-22 10:20:00  Updated vendor data. 100005                https://mycompany.autodeskplm360.net/...