Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Incorrectly formatted phone number in OTBI table
Summary:
Content (required):
Hello! I have noticed a situation in our Fusion tables that I'm curious about resolving. We are currently seeing two phone numbers for two different phone types that have different formatting. We're using the field in some integrations so it's being fed inconsistently downstream.
We are seeing the phone number with dashes on the front end regardless of how the person entered the information but it appears as below in the tables.
What causes the phone number to be submitted in these different formats and is there any way to normalize that format so we can send consistent data downstream?
Tagged:
0