Skip to Main Content

Customer Solutions

Announcement

This area allows you to enter ideas for Oracle Utilities products. You can help promote an idea by:

  • Being as specific as possible about your request.
  • Clearly articulating the benefits. For example, reducing implementation effort or reducing cost to serve.
  • Calling out if you have seen this requirement from other utilities.
  • Voting for suggestions you think should be implemented.

Resolve discrepancies in saving phone numbers via UI vs. IWS

Kalusinghe Ranasinghe-OracleJul 23 2024 — edited Aug 8 2024

In C2M we are noticing discrepancies when phone numbers are being saved when entered via the UI and IWS:

  • (416) 560-1000 was entered via the UI and it formatted the number according to the formatting algorithm on the Person Contact Type.
  • 2895601000 was inserted via C1-Person IWS and it does not format the phone number when saved to the database.
  • Adding in 2895601000 via UI was saved with the correct formatting, now resulting in duplicated person contacts.

Trying to pass in “416” or “416-560-1000” via C1-Person IWS results in an error message “Contact Value format is incorrect. Must be (999) 999-9999"

Similar error message should be received when 2895601000 was inserted via C1-Person

When adding a new person contact via UI/IWS there should be a check for duplicates.

This would resolve and reduce issues encountered by clients during integration solutions and improve data quality.

Comments
Post Details
Added on Jul 23 2024
Closed - Alternative Option
0 people have voted for this idea
3 comments
269 views