- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2025 11:25 PM
Hi,
I have a requirement create new field (mobile phone number) and remove mobile phone field but if I delete this existing field it can delete all mob no. So, I want to take back up of 2104000 record in ServiceNow and again import it in user table. What is best method which can take less time in restoring data and won't affect on integrations.
Regards,
Himanshu
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2025 11:31 PM
Hi @himanshuraw ,
As per your requirement if you want the field "mobile phone number" on user table you can just the rename the existing "mobile phone" field with "mobile phone number". I think that is better solution without any customization.
Here the path to do so-
Step 1: - Right click on the field to open the dictionary of that field.
Step 2:- In the related list of field dictionary, double click to rename the name of the field as "mobile phone number".
Please accept my solution and give it a thumbs up if it's helpful for you.
Regards,
Prashant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2025 11:31 PM
Hi @himanshuraw ,
As per your requirement if you want the field "mobile phone number" on user table you can just the rename the existing "mobile phone" field with "mobile phone number". I think that is better solution without any customization.
Here the path to do so-
Step 1: - Right click on the field to open the dictionary of that field.
Step 2:- In the related list of field dictionary, double click to rename the name of the field as "mobile phone number".
Please accept my solution and give it a thumbs up if it's helpful for you.
Regards,
Prashant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2025 11:37 PM
This sounds like a very weird requirement. What is your business case? Why not just change the label of the existing field? You have a field there and you are creating another one to store the same information and delete the existing one? Please explain the 'why' behind this.
Next to that: don't make a backup. That's a waste of time. If this (for whatever reason) truly is a valid business requirement, create the new field, copy the value from the existing field to the new one and only after validating that it's all correct, delete the old field.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark