The Valid Custom Inventory Data Types
dougj
November 12th, 2008
It is a misnomer to state that Custom Inventory supports certain data types. Within the aexcustinv.exe process, all data is treated as a string type. It is incumbent on the Notification Server dataloader to interpret the data types defined in the column attributes, create the table properly in the database, and validate the incoming data.
So, it is a clearer to say that when creating custom inventory XML scripts, certain data types can be processed by the NS dataloader.
Currently, the dataloader will process the following data types:
| Custinv Data Type | Converts to SQL Data Type |
| string | nvarchar |
| int | int |
| dateTime | datetime |
| r4 | real |
| float | float |
| i2 | smallint |
| number | numeric |
| boolean | bit |
| uuid | uniqueidentifier |
| bin.hex | binary |
| currency | money |
Note: These are case sensitive, so dateTime must be specified with a capital T in Time.
Note: The number data type requires a precision and scale specification. An example is attached to this article.
The following image shows the database schema for the attached sample inventory.
| License: | AJSL By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License |
| Support: | User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab. |
dt:maxlength is only required...
The dt:maxLength element is only required for string and bin.hex data types. It can be completely removed/unspecified for all others.
Would you like to reply?
Login or Register to post your comment.