Francis von Stein Posted November 14, 2019 Posted November 14, 2019 Hi. To enable effective asset management it's important there is a unique identifier. As the "Name" filed is the main mandatory filed it will be used as our unique identifier field, holding asset tags. Server names, Database names etc. There is no validation on it or any other field. Can validation be enabled against the "Name" field so that no duplicate asset can be added It would also be good to have the following added to "State" and "Operational state" so they are more reflective of an asset life-cycle. Then I can add the relevant sub states , Rather then having to use "Current" as Stock and "Active" as in use State Sub State On Order None In Stock Available, Reserved, Defective, Pending repair, Pending install, Pending disposal, Pre-allocate In Use None Retired Disposed, Donated, Vendor Credit Missing Lost, Stolen Operational State Production UAT Test SIT Thanks
ArmandoDM Posted November 14, 2019 Posted November 14, 2019 Hi @Francis von Stein at the moment there is no validation about duplicate names, but we have a story on the pipeline to let you specify unique fields on assets in order to prevent duplicates. As far the list of 'State' and 'Operational State', I will mention your requirement to the relevant people and get back to you. Regards Armando
Francis von Stein Posted November 14, 2019 Author Posted November 14, 2019 @ArmandoDM Thanks for replying. Can you please explain a bit more how that would work If I add a unique field to say, "Computers" will all assets entered under that class type get the same unique filed? meaning I could duplicate, or will that filed have validation behind it to stop that? Or will it be a unique field for each individual asset added under any class? In either of those cases as we will be importing/updating/adding attributes to assets in an automated process via discovery tools - would that them mean mapping the output to every asset to a unique filed for each class or individual asset? rather then a single consistent filed like "Named" Thanks
ArmandoDM Posted November 14, 2019 Posted November 14, 2019 Hi @Francis von Stein if you specify that a field must be unique, then you will be prevented from creating a new asset which would be a 'duplicate'. There will be validation. The validation should be per Asset Type. However you try to import/add/update an asset, there will be a validation on the unique fields defined on each asset: if you try to add a duplicate, the action will fail. Hope this makes sense? Regards Armando
Nikolaj Posted December 20, 2019 Posted December 20, 2019 Hello @ArmandoDM How is it possible to specify a field as unique for an asset type? I cannot find it. Thanks Nikolaj
Francis von Stein Posted February 4, 2020 Author Posted February 4, 2020 @ArmandoDM An update on this would be appreciated. Thanks
ArmandoDM Posted February 4, 2020 Posted February 4, 2020 Hi @Francis von Stein the change is still in the queue, not being worked yet. You may have a look at the current stage for the change in the Success Portal I will add you and @Nikolaj as interested connections. Regards Armando
Nikolaj Posted February 4, 2020 Posted February 4, 2020 2 hours ago, ArmandoDM said: Hi @Francis von Stein the change is still in the queue, not being worked yet. You may have a look at the current stage for the change in the Success Portal I will add you and @Nikolaj as interested connections. Regards Armando @ArmandoDM ....yes please Thanks, Nikolaj
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now