I wouldn't actually recommend changing what attribute is set to be the IsName attribute. The IsName attribute is used in multiple part of the product. It is the main attribute you see in drop down lists as well as the value you see in the list in Configuration Management.
It's probably the attribute used for any data import that you might have to match up with a unique value.
I would always suggest to have a unique value in here and then you can have a second title on the Configuration Item Object where you can enter any values that might not be unique.
For any queries you can then add both attributes as columns and when used as drop down lists, you can use a template to show more than one attribute if needed.
Thanks Jenny. I thought that might be the case.
If we start using a second attribute as the "CI Title" is there any way we could auto-populate the original Is Name with an incrementing value. i.e. CI0001, CI0002, CI0003?
Or would it always have to be manually populated?
There is no feature that will allow you to rename all of your CI's in an incrementing way.
You could however, do so in a 3rd party tool, like excel and then import all the CI's into your Service Desk.
Please be aware thought, when doing this that if you already have CI's in your Service Desk system, you might be getting duplicates as you are looking to change the unique identifier.