Displaying the Asset unique ID
Hello all,
When you create an asset it is assigned a Unique Asset ID number.
Is it possible to view this as a column header when viewing the long list of Assets? (i.e. Assets > View by All Items)
I'm thinking of using the Unqiue Asset ID as part of the asset's naming convention. How does everyone else do it?
StuBox
When you create an asset it is assigned a Unique Asset ID number.
Is it possible to view this as a column header when viewing the long list of Assets? (i.e. Assets > View by All Items)
I'm thinking of using the Unqiue Asset ID as part of the asset's naming convention. How does everyone else do it?
StuBox
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
GillySpy
14 years ago
Displaying the ID in this way is not possible, however, you could run a report and get this. The ID is ASSET.ID. Reporting on assets uses meta data so it is not necessarily intuitive. What do you use the ID for?
Posted by:
stubox
14 years ago
Thanks GillySpy
Well I was thinking of using the Unique ID as part of our asset naming convention, or perhaps even THE naming convention. i.e. name a PC or switch the number generated by Kbox e.g. a PC called PC10784 , if it was a switch SW10784, thin client terminal TC10784.
I'd have to create the asset leaving the Name field blank, then afterwards open up the asset record to view the Unique ID and manually enter in the Name.
So having the ID column header would be useful...........but now that I think really about it, this is a silly question because the Name field will appear as a column header anyway!
Ok in that case forget the original question! What do you think about this approach for an asset naming convention? As long as the name is unique it doesn't matter to me what structure it takes. I'd be interested in hearing how others name their assets and if it is automated?
Well I was thinking of using the Unique ID as part of our asset naming convention, or perhaps even THE naming convention. i.e. name a PC or switch the number generated by Kbox e.g. a PC called PC10784 , if it was a switch SW10784, thin client terminal TC10784.
I'd have to create the asset leaving the Name field blank, then afterwards open up the asset record to view the Unique ID and manually enter in the Name.
So having the ID column header would be useful...........but now that I think really about it, this is a silly question because the Name field will appear as a column header anyway!
Ok in that case forget the original question! What do you think about this approach for an asset naming convention? As long as the name is unique it doesn't matter to me what structure it takes. I'd be interested in hearing how others name their assets and if it is automated?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.