E51 Outlook phone number Field.

Hi,
I'm having a problem with my E51, when using PC Suite to sync with Outlook.
When a new contact is added via the phone, and then synced with PCSuite, the Phone Field entry in Outlook is set to Other, even though on the phone it's set to Telephone:
Is there any way to change what field name is used?
I have the latest firmware for my E51
PC Suite is v7.0.7.0
MS Outlook is 2007 SP1
Thanks.

Just to confirm I am having the same problem (sorry not much help!). The 'Telephone' field in the E51 maps to 'Other Telephone' in Outlook 2007 and then 'disappears' when synched with my Revo. I have had to cut and paste the 'Telephone' field to the 'Telephone (home)' field on all my phone contacts and that has kept it under control.
If when adding a new contact in the E51, the default field was 'Telephone (home)' then I would be happy. It does not seem possible to change the entry default? At the moment it means having to remember to add this field every time I need to add a new contact's home phone number. The 'mobile' field works fine.

Similar Messages

Address Book/iSync - email addresses moving to phone number fields

I'm not sure what is causing this, but I'm noticing that email addresses in my cards are moving to phone number fields. I originally thought this had something to do with cards that had no phone number in them, only an email address, but now I"m realizing that's not the case.
I fixes all cards last night and just a minute ago, when I was in Address Book I noticed some or all of the email addresses had moved again. I reverted to my backup from last night and it fixed things, but I'm wondering what's going to cause those addresses to move again.
I do use iSync to sync my AB contacts to my Motorola phone (I think I have it set up where it's one way, computer to phone) and I have Entourage that's using my AB contacts to populate its address book.
Any thoughts about what in my environment is causing this?
-John

Thank you for the suggestion. I did this, but noticed that some cards were still messed up. So I reverted back to a clean copy of my address book from last night. Then I went to iSync and synchronized with my Motorola phone. That's when iSync says that it's going to modify over 5% of my contacts in AB (122) at which point I said okay. Problem appears to be that the cards it modifies is random.
Now to make matters worse, it appears that if I repeat this process over and over (revert, iSync, look through cards), there is no pattern to which cards are changing. I don't even know how to troubleshoot this. I'd love make iSync go one way - computer to phone - so that the phone can never write information to the computer. Is that possible?
I'm sure this needs to go to a different section...
-John

How to prevent users from entering '+' or '0' in front of country code in the phone number field?

Requirement:
How can I prevent guest users from entering '+' sign or '0' in front of country-code in the visitor phone number field during self registration?
Few SMS service providers are not looking for '+' sign or '0' or '00' in front of the international phone numbers to trigger the sms. Providing these values in front of country code during self-registration may fail to deliver the sms to recipient.
Solution:
Using a simple regular expression, you can validate the entered phone number during the guest registration.
The below regular expression will help you to validate the phone number and allows to register only when the phone number is not staring with '+' or '0'.
^[1-9][0-9](\d{7}|\d{8}|\d{9}|\d{10}|\d{11}|\d{12})$
It also performs the below validations.
only numbers are allowed.
first digit of the entered phone number should be 1 to 9, so '+' or '0' is not allowed.
numbers from 0 to 9 are allowed from the second digit.
also validates phone number length, the length of the phone number should be 9 to 14.
Configuration:
To add the above regex in the visitor_phone number filed, please navigate to ClearPass Guest >> Configuration >> (Pages)Guest Self-Registration >> select the self-registration page and go to Edit >> Register Page >> Form >> select the filed visitor_phone and set the Validator to " ISRegexMatch" and enter the above regex in the Validator Argument filed as shown below.
Note: Edit the Validation Error as per your requirement.
Verification
Adding the given regex will validate the phone number and prevent the guest user from registering the phone number starts with '+' or '0'.
Please find below the sample outputs for your reference.
Result when phone number starts with '+' or '0'.
Successful registration.

Is this a Mac Preview issue?

Phone number field

I am trying to create a phone number field that will automatically create the dashes as they are typing in the numbers. For example: i type 222 and a dash follows after the last 2 automatically. I know about the regular expression validation you can set, but it is a little complicated for the end user.

Add the JavaScript to the HTML Header field of the Page definition.
Then add the following to the HTML Form Element Attributes of your field:
onclick="javascript:getIt(this)"However, be aware that the Javascript function in the example expects a particular document structure - it is not written generically so you will have to spend some time updating the example OR find another one.

Missing General Phone Number(field TYPE)while PC S...

Hi
When I sync my phone with Lotus Notes 7 via PC Suite, the General Phone field type didnt get sync accross to my Lotus Notes 7 Address book. Can someone let me know how I can resolve this problem? At the moment whenever i enter phone number through my mobile phone, i have to change the type to office/mobile in order to successfully sync with Lotus Notes 7. I noticed Lotus Notes 7 Address book doesnt have the General Phone field type hence data will be missing during sync.
Here is the Operating Platform
Windows XP Professional SP 2
PC Suite 6.84.10.3
Lotus Notes 7.0
Hand Phone MODEL: 6500S
Connection: Bluetooth
Thanks
Cheers!
DK

Just to confirm I am having the same problem (sorry not much help!). The 'Telephone' field in the E51 maps to 'Other Telephone' in Outlook 2007 and then 'disappears' when synched with my Revo. I have had to cut and paste the 'Telephone' field to the 'Telephone (home)' field on all my phone contacts and that has kept it under control.
If when adding a new contact in the E51, the default field was 'Telephone (home)' then I would be happy. It does not seem possible to change the entry default? At the moment it means having to remember to add this field every time I need to add a new contact's home phone number. The 'mobile' field works fine.

0 in Phone Number Field

Hey all,
I was just wondering is there a way to display a phone number with the 0 at the beginning of the number. This isn't a requirement, but I would like to. Would help the user.
I have already made the tables and inserted the data. I have searched about the net with not many results.
The number field is 11 digits and as a result of this problem I have had a few numbers with 11 numbers that aren't 0. I figured this would also assist error check and avoid any anomalies in the data.
Could I run a script to correct this problem? or would it be in APEX attribute settings?
Any help would be appreciated :)
Thank's in advance.
Edited by: 948251 on 02-Aug-2012 10:52

948251 wrote:
Hey all,
I was just wondering is there a way to display a phone number with the 0 at the beginning of the number. This isn't a requirement, but I would like to. Would help the user.
I have already made the tables and inserted the data. I have searched about the net with not many results.
The number field is 11 digits and as a result of this problem I have had a few numbers with 11 numbers that aren't 0. I figured this would also assist error check and avoid any anomalies in the data.
Could I run a script to correct this problem? or would it be in APEX attribute settings?
Any help would be appreciated :)
Thank's in advance.
Edited by: 948251 on 02-Aug-2012 10:52Of course, the best way to fix it is to use the correct data type in the first place. Just because it is referred to as a "phone *number*" doesn't make it a NUMBER. Neither a telephone "number", nor a US Postal zip code, nor a US Social Security "number" have any properties of numbers. You would never do any mathematical operations on them. They are really just character strings which, by convention, are limited to the same characters that are used to represent numbers.
And now you are dealing with one of the problems of using the wrong data type. Fortunately, this is not as severe as using the wrong data type for a DATE.

SMS and Outlook Phone Number Extenstion

I don't know if this is a N95 or a PC Suite problem.
I have used different computers, PC Suite versions and N95 firmware versions to test this.
I create a contact in Outlook and add a phone number.
For examle:
Country: Germany
Area Code: 123
Phone Number: 4567
Extension: 89
This is shown as +49 (123) 4567 x 89 in Outlook and
this is synced as +49 (123) 4567 x 89 to my N95.
I like the x so I can see the extension easily. But when I
try to write a SMS and select this contact and the phone
number, I always get "Invalid Contact details: ..."
Is this a problem with my N95 or with the PC Suite? I cannot
enter the "x" manually in my phone so I think this shouldn't
be synced. But it would be nice if I could enter it.
Marc

I pretty much agree. I have an N95 and also use Outlook 2003. I sync using PC Suite (6.85.14.1). I'm pretty sure I did not have this problem with my previous phone (6680) but if I use the formatting for the phone numbers as provided by Outlook 2003, then they get synced to the N95 as something like +44 (07801) 123456. The N95 will not work with that number so I have to edit them before I can use them - tedious.
In fact, it is only necessary to delete the nought at the beginning of the area code, so +44 (7801) 123456, will work.
It would be very helpful if the N95 software could spot the international code and then ignore a following nought. Maybe that doesn't apply to all countries, but I guess it would help a lot of us!
MAW.

Need to have Phone Number field as just numbers with no formatting.

We have a web service that is passed the work phone field from the contact object. That WS uses the phone number to auto-dial the customer's number for our sales reps.
My issue is that the WS expects to just see the area code and the phone number as digits as 1235554444. It has been working fine for over a year and recently been failing as now the numbers come in with a "+" sign.
The format seems to change depending on the time of day I look at the fields and is random for each user. The company profile is set to USA as the default and so are the user's locale settings.
How do I make the "+" go away?
I have tried various settings and couldn't seem to find one that didn't give me the formatting. I've also tried to copy the work phone field to a hidden field and using WF to strip out the "+" but there seems to be no way to do a REPLACE() function in a WF rule.
Any ideas?

So after spending enough time with this I was able to find a way around the issue. Ultimately I needed a phone number format that was fixed and would not mask the data per the user's locale settings. It also needed to be just area code and phone number shown as 1112223333.
On the contact object, a new field was created as a Short Text. Then a WorkFlow as created that copies over the value from the WorkPhone field into this unformatted number so that it can be passed to our Web Service.
It took a while for me to figure this out since if you just use the WorkPhone variable you get all the masking based on locale. I didn't have the functions available to me in the WorkFlow to just strip spaces and "+" or "( )" so I needed it to be as close as I coudl to just a basic phone number. By using the FieldValue() function it seemed to take a number like 1 (555) 444-4444 and return 1 555 4444444. This works no matter if it was +1 555 4444444 or +41 555 4444444 so I could then use some pattern logic.
This is what I used to copy that data over to my temp/work field which is now passed to our click-to-dial function.
Mid(FieldValue('<WorkPhone>'), InStr(FieldValue('<WorkPhone>'),' ') + 1,3) + Right(FieldValue('<WorkPhone>'),7)

OVi Suite is destroying OUTLOOK phone number form...

I have formatted my Outlook phone numbers the standard way +49 (yyy)xxxx. With Ovi Suite sync of contacts, the brackets are now removed from the phone. Since you cannot specify the sync direction the reformatted phone numbers are soon or later ending up in Outlook. The issue: I don't know which part of the number is area code and what is the number. I had to retype all my 250 numbers using a 10 year old printout. This is not acceptable.
My OVI Suite is the current and called now Nokia Suite.
Best is to remove that stupid filter or allow for synch direction in OVI Suite.
Is there a solution that I have overlooked or do I have to install the old PC Suite in addition for syncing contacts?
I cannot not live with this issue.
Best regards
Michael

Hi Hunchback,
why can't we just have a software switch or sync by directions as in PC Suite? As I said even when I do not touch my contacts in the phone I have all Outlook contact formatting removed . I have definitely not touched all contacts in the phone. I assume it happend when you reload backups on the notebook, reinstall Ovi Suite and then synch.
All my phones E72, N82, E61I and N8 can live with formatting.
Best regards
Michael

E71 MS Outlook phone number format

How do I remove the leading zeros from numbers stored in Outlook when synching with E71? One problem is that Italy NEEDS a leading zero [i.e. +39 (0)nnnn nnnn]. Currently most numbers in Outlook are stored +nn (0)nnnn nnnnnn - but I have too many stored to do this manually. Any suggestions?

Thanks for your response. I'm not complaining about Outlook - what it does seems reasonable to me - but I was hoping for a solution to removing those leading zeros when synching with a mobile (where they get in the way of making a call).
Its possible to export to a csv file in Excel, then doing a variety of search and replace exercises, then upload again to Outlook (new folder), then synch (new folder) to the phone. BUT it's not the kind of job to do every week! Surely someone has done this commercially?
JubJub

Text messaging error: please enter a phone number

Lately, whenever I get a text message and go to respond, I am asked to enter my phone number. I enter it, but the next time I get a text message, the 'my phone number' field is again blank. Anyone have an idea what may be going on here and how to fix it?
Iphone 4S 32gb phone running OS 5.1.1.

Hi
please run BDLS first with Source as your Source system client and target as your QAS system client
and run BDLS for each clients in your system
then try to create Entry in WE20 .
you should be able to do so .
Regards
Dishant.

Save a phone number without the input mask

Hi,
I actually have 2 related issues that I hope you might be able to help me with.
I have a form linked to an interactive report, so when I click a record, the form is populated with the record's data. I just started using the new text field masked input plugin to handle phone number formatting, etc., which Patrick recommended.
The plugin works nicely when a phone number being displayed from the source is 10 characters. The input mask I'm using is (999) 999-9999. However, I also have phone numbers in records that don't include the area code. When I select one of those records, the phone number field is blank. I would like it to display 999-9999, and be right justified. Is there an easy fix for that?
My next problem occurs when I try to save the record. The process tries to save the phone number, including the mask, (14 characters), to the table. I only want to save the number to the table, excluding the mask. I'm sure there is a way to do this but I haven't found it yet.
Thanks in advance for any help,
Gary

This is my solution to parsing the number only from the masked phone number:
1) Create a field, 'P1_PHONE_MASKED', with a phone number mask: (?***) 999-9999
2) Create a hidden Database Column like: 'P1_PHONE' It will initially hold the value of the record's phone column.
3) create a javascript function in the page's before header section, between the space tags, to strip out all non-numeric values and update the hidden field:
function remmask(src,tar){
var mystring = $x(src).value;
mystring = mystring.replace(/\D/g,'');
$x(tar).value = mystring;
4) Place the function call in the from in the HTML Form Elements Attributes of P1_PHONE_MASKED: onBlur="javascript:remmask('P1_PHONE_MASKED','P1_PHONE');"
Now, anytime you change the value in P1_PHONE_MASKED, P1_PHONE gets updated with just the number values from P1_PHONE_MASKED.
You can also add validation to the function to ensure that the length of the phone number is either 7, no area code, or 10, including area code. Normally, the mask should handle validation, but as you can see, to make this work, I had to make the mask more flexible, to allow for alpha numeric values in the first 3 positions and to allow for either 7 or 10 characters. Unfortunately, that means a user could enter something like XXX12 and the mask won't reject it.
Partial solution to displaying ( ) 999-9999 in the masked input field P1_PHONE_MASKED when initially selecting a record for display.
1) Make the Source Type for P1_PHONE_MASKED "SQL Query"
2) Insert a query similar to the one below into "Source Value or Expression"
SELECT
CASE
WHEN length(METAREPO.CONTACTS.CONTACT_PHONE) = 10
THEN
METAREPO.CONTACTS.CONTACT_PHONE
WHEN length(METAREPO.CONTACTS.CONTACT_PHONE) = 7
THEN
'___'||METAREPO.CONTACTS_2011.CONTACT_PHONE
END
FROM METAREPO.CONTACTS
WHERE METAREPO.CONTACTS.CONTACT_ID = :P1_CONTACT_ID
This will display 7 digit phone nubers as follows: (___) 999-9999 in the masked field: P1_PHONE_MASKED.
I wanted to use spaces between the () to make it perfect, but I'm unable to get this to work. I've tried things like:
' '||METAREPO.CONTACTS_2011.CONTACT_PHONE
LPAD(METAREPO.CONTACTS_2011.CONTACT_PHONE,3,' ')
Both of which work in PL/SQL Developer, but not in Apex. I believe this is because HTML collapses spaces by default.
I would like very much to resolve this last issue. Any suggestions?
Regards,
Gary

Web form: can't get phone number to show up in email notification

http://www.rockmitzvah.com/contact/contact4.htm
trying to add a phone number field so my client can call leads. I have tried the phone number field both as required and not. The resulting Thank You screen and email just show this without the phone number:
Summary of web form submission:
Your Name
j a
Email Address
[email protected]
Case Number
4388779
Message
phone number
Is it a workflow issue? How do I fix it?
thanks
j

Hi there,
Your phone number field name doesn't match any of the BC's phone number fields. You have name="PhoneNumber" there, but BC names are name="HomePhone" and name="CellPhone".
Try reinserting that form onto a page and submitting it.
Cheers,
-mario

ESS Family Screen - Issue validating Phone Number

I am having a problem with the Family contact screen and the validation on the phone number field. I am not the original developer that worked on this screen and do not have access to that person, but I think this issue is caused by SAP delivered code, and not anything we did here.
If I enter a phone number that has more than 7 digits (ex. 12345678), but I do not include a dash in the number, I correctly get an error that says , "Telephone number must consist of seven digits"
If I include a dash in the number (ex. 123-45678), that validation does not detect the error and I am allowed to proceed to the review screen, where the phone number is displayed exactly as I typed it in, but when it gets saved, the extra digits are truncated.
I'm willing to code my own validations on this field, but I don't know where to put the code. Can anyone please help?

Could you please mention ESS BP version that is been used? If it is, you can search for Note in SMP, if not found, raise one. This could be an issue with standard SAP code. However, as you mentioned the application been changed, review the changes been made as well.

Phone number concept

It seems to me that the phone number concept in Maemo (don't know in other platforms) is maybe correct in technical sense, but not in usability sense. Let me explain.
The phone number field allows only a limited set of characters to be input: 0-9, *, #, p, w (anything else?).
At first glance, this seems to be a good idea, in order to prevent users to enter letters for instance, by mistake.
In fact however this is a severe limitation, for the following reasons:
1. If I want to read the phone number, it is quite difficult to visually follow long numbers, for instance if I want to check it, read it to someone or use it to dial on another device. It is much better to separate the number in shorter clearly distinguishable groups by spaces or dashes.
This however cannot be done on N900 on the phone.
Spaces can be entered in Ovi Suite, these are even transferred to the phone, there is no problem to make a call properly, but the phone is not able to identify the caller if the number is entered with spaces.
2. It is very good, that multiple phone numbers can be assigned to a single contact. It is also excellent, that there are field labels allowing to distinguish variants such as telephone - telephone home - telephone work etc. (by the way, an icon would do a better job)
But, there are numbers for a contact, where these labels are not sufficient and additional note or tag is needed, for instance a phone to neighbors, secretary, temporarily out of service etc.
There is no possibility to enter these notes, other than entering a new contact with the specific tag, but in such case the nice feature of having all numbers of the contact in one record is lost (and with 1500 contacts, this solution would even make it worse).
Since my old (6 years) smartphone has this possibility, as the numbers were imported into the N900, they came also with the tags written behind the number in brackets. But, this time N900 is not even capable to dial these numbers. In order to get the numbers functional, I had to remove all these tags manually.
I must say that I feel this as a strong drawback of the contacts features and it can make me even to drop N900, because I simply need support for such information and workaround is too laborious.
I suggest, that instead of putting limitations to the user, it would be much more useful to simply dial all numbers found in the number field (processing properly the +, *, #, p, w, of course) and leave out anything in ( ) brackets (for instance). It is so simple!
If an old smartphone can do this, I expect that tablet should be also capable of an intelligent approach.
If the entry limitation is really considered as benefit for users, ok, as an option it is fine, even as default setting. But it should not be killing the usability.
Is there any solution to this issue?

you've raised some good points, but imho its getting worse, not better..
With regards to tags, this is something I think pioneered on Nokia handsets (first time I saw it was on the first Symbian S60 7650 phone)
Each number has a type: business, fax, mobile, home, phone
and each number has a tag.. the defaults now are blank, home, business.. but on S60 handsets you can give them tags..
Business Phone (helpdesk) 1234567
Business Phone (reception) 5553333
for example is something I had on my phone for the place I worked..
However, The N97 (iirc) was one of the first S60 handsets to loose this ability.. The 5800 handset, the first S60 5th edition, had the ability, the N97 (the second S60 5th edition handset) did not.. and the N900 does not..
Bring back custom tags.. its very ordinary without it..
I doubt we'll ever see them on a Maemo / Meego handset

E51 Outlook phone number Field.

Similar Messages

Maybe you are looking for