Data management tool is the best option to update the phone number, otherwise if you are having less number of records to update phone numbers then you can follow below steps to update phone number directly on People form:
If you have a permission of CTM:People form then you can directly update the phone number, PFB screenshot:
Open CTM:People, search the people record which you want to update phone number , then goto more details tab and update the phone number.
Click on above edit option update the phone number and save it.
We have bulk records to update on Phone Numbers.
Is it something that can be done from Data Import or only through Data Management tool.
What is the process/procedure to follow using Data management tool.
Appreciate any other suggestions/further updates on this requirement at your earliest availability/Convenience.
are you only interested in updating phone numbers in CTM:People, or would change have to be applied to all (active?) requests associated to those records as well?
Its only for the CTM:People as of now.
If any Information on it kindly share.
Appreciate response at your earliest availability.
If goal is not to set up an integration, but to perform a one-time update, even a simple transformation prepared and executed in Spoon should be able to update phone numbers as long as it is given enough information to identify correct records. Ideally, it would be fed Person IDs (which are unconditionally unique), Corporate IDs (which might be unique only up to scope of Company), or Remedy Login IDs (which should be as unique as Person IDs are, but may not be) and new phone numbers (Phone Number Business?) either via file (e.g. .csv or .xls), direct database connection or webservice (e. g. REST) and tasked to perform update of phone number; matching by person's name is possible, but probability of duplicates (which can be discarded by action's settings) would be much higher.
Here are two relatively recent discussions which dealt with similar requirements, albeit different attributes:
Pushing "Locale" value in "AR System User Preference" form. where the same value was written to all records (it contains description of transformation consisting of three actions, first two of which would be replaced by action which retrieves data, and the third would have to be adjusted to your requirement -- ARUpsert action would have to update records in CTM:People where 'Person ID' = $Person ID$ by populating phone number from input into appropriate attribute, probably Phone Number Business), and
How do we update Manager Name on people profile for bulk users using DMT? where use of DMT was discussed.
1 of 1 people found this helpful
If it is just a one-time update, then I've successfully used the Data Import Tool. You have do download key values to a CSV, Correct them in a spreadsheet and then you can save the results as a NEW CSV file and upload them back, using the Data Import Tool again.
Since you have the ORIGINAL CSV file, you can always go back if you mess it up.
I like taking the Person ID as my key and whichever phone number you want to manipulate.
If you want to fix the whole quartet of Country Code, City/Area Code, Local Number and Extension, you'll have to use an AR System report instead of a Web report because those values are not available in a Web Report.
The reason that fields Geo mentions not being visible in Web Report is their (intentional) omission from view, but their values are stored in database. If in doubt how to identify them (though they do include "Business" or "Home" as part of name) look at active links associated to buttons used to enter them separately -- they all include Open Window action whose On Dialog Close Action fields list them (e. g. CC Business stores country code of business phone number, while CC Home stores country code of home phone number).
I haven't done a People Load since 9.x and, back in the day, the People Load was what actually caused a lot of the issues. No matter how careful you were with the spreadsheets, Atrium Integrator just couldn't handle a text field with all numbers very well
That's where I learned to correct it with the Data Import Tool.
We did try the Data Import tool on our Non Prod Environment and it did work fine.
Will try the same on our Production as and we have the request for it.
Hope this is the direct approach of using Data Import tool as its onetime task.