As I understand it, when creating custom asset types the first field in a table is automatically created and named "name". In one forum post this field is identified as a unique key. In one of the asset management videos however the "name" field is shown with several non-unique values. Also I understand that there is a record ID automatically created for each record.

Is is necessary to have or use this "name" field?

Can it be renamed?

Is it designed as a key and therefore must be unique?
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer

it is not unique, but you would be well advised to treat it as unique since the ID is not obvious in the UI. It is commonly flagged as unique "PK" when importing data from a csv. You can flag any field (or combination of fields) as the "PK" for a given import, but it's not relevant to database structure since IDs will keep everything unique anyway.
Answered 02/13/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


The Name field is required in the asset type and must be called name; but can be null in the asset itself. As Gerald said, it does not have to contain unique information. You'll often hear it called the key, because it always exists. The name field is the only fixed field because we have to have something common to query to display data in other places that leverage the assets such as tickets, or other assets that have a linked asset type field.

Hope that helps.
Answered 02/13/2012 by: cblake
Red Belt

Please log in to comment
Thanks, I understand what's happening now.
Answered 02/15/2012 by: depoteet
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity