Change the reference table of CauseByChange field in Incident form

[MohitSaxena]

I received one request to change the reference table of CauseByChange field present in Incident form from Change table to Task Table, and Change its lable to only 'CauseBy'.

But my lead suggested me to create a new field instead of modifying the current field. what could be the reasoning for doing that I could not understand. Why It's best practice to create a new field not changing the existing one? 

[Ankur Bawiskar]

@MohitSaxena 

it's an OOTB field, why to touch it?

It's best not to change any field type for OOTB field.

Impact:

• if you change field type, data loss will be there
• reports, business logic etc might break
• when upgrade happens it may have conflict
• changing field type and changing the reference might confuse admins or developers in future

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

[Ankur Bawiskar]

@MohitSaxena 

Hope you are doing good.

Did my reply answer your question?

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

[Dr Atul G- LNG]

Hi @MohitSaxena 

I wouldn’t recommend creating a new field or changing it to the Task table. The primary reason for this change is Incident, as per ITIL standards. If you change it to Task, you’ll get more types of tasks recorded, which might lead to users complaining about too much data.

If you still want to proceed, you’ll need to override the dictionary override and update the reference to the Task table.