Impact on the change on change table

[Nagesh5]

Hello Team,

We have recently(6months back) implemented ITSM for one of the client and our query related to change management we have earlier tree picker when selecting location on the change record and now customer requesting to change to list instead of tree picker and our question is there any big impact changing this attribute?

@Ankur Bawiskar 

Thanks,

Nagesh Kavala

[Ankur Bawiskar]

@Nagesh5 

is that an OOB field or custom one?

I would suggest not to change the field type for that field as it will clear data from records of CHG.

If it's still in DEV and field not migrated to higher environment then go ahead and change field type if system allows.

If this field is migrated already to UAT or higher environment then create another list field and store the value from reference to list field via 1 time scheduled job and deactivate the reference field

Please discuss this approach with your customer as well

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Nagesh5]

thanks for the comments on my post sorry for the confusion and we are not changing field type here.

Customer just wants while searching location the details appearing as a tree picker instead of the his looking for the list display for reference field. So our question if we change the pick list from tree picker to list any high impact or any issues?

[Ankur Bawiskar · Accepted solution]

@Nagesh5 

tree picker is just an attribute on reference field.

if you remove the attribute and field type is same then no impact.

Just that they won't see the hierarchy while selecting the values.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Nagesh5]

so there is no impact on any other place right(like scripts, reporting and other places)?