Unformat display mask before saving phone number

[ecalan]

This should be simple:

I have had an app with grids where the detail view formats the display of phone numbers with TRANSFORM(remspecial(<value>),"@R (999) 999-9999") and in display unformat Remspecial(<value>) unformats so only the numeric value is saved to the database. This is important for consistency in the search phone number function in other parts of the app. It has worked great without any issues.

I am developing a UX based upgrade and I can not figure out how to similarly unformat from the UX mask function before saving and the "( ) - " is in the saved field.

What am I missing?

[GGandhi]

Re: Unformat display mask before saving phone number

go to the afterdialog server side event and before the
ExecuteServerSideAction("Save Data::Save_Submitted_Data_to_Table_s_") line

add e.dataSubmitted.phone = remspecial(e.dataSubmitted.phone) ' substitute any name you gave for the phone field

[ecalan]

Re: Unformat display mask before saving phone number

Govindan,

Thank you for the assistance. I will not be able to try it out until later but wanted to thank you right away. I will post that it was successful - which it seems sure to be.

[ecalan]

Re: Unformat display mask before saving phone number

Worked great but one clarification and a follow-up.

If anyone else comes across this, my phone field was in a repeating section, so my syntax was:

e.dataSubmitted.phone[1] = remspecial(e.dataSubmitted.phone[1])
e.dataSubmitted.phone[2] = remspecial(e.dataSubmitted.phone[2])

(Hopefully I save someone the hour I spent with variations of .phonetable.phone)

Follow up:

My App was running for about a month before I realized the search wasn't working quite right after using the UX to connect to a DB that had been fronted by a grid, so I have several hundred entries that have the formatting characters. How do I update the existing data to remspecial()?

[GGandhi]

Re: Unformat display mask before saving phone number

good you got it working.

my phone field was in a repeating section

are you limiting phone entries only to two entries?

after using the UX to connect to a DB

you should be able to do via the db itself.
what database backened you are using?

[ecalan]

Re: Unformat display mask before saving phone number

are you limiting phone entries only to two entries?

Yes, and I actually removed the add rows button from the repeating section because of the issue that caused you to ask the question. I know it's doable to have dynamic rows keep the formatting functionality but it seemed fairly complex and it just wasn't very important for my app. It is the intake form and the single record form allows for 4 entries - wouldn't want more -where rare complex contacts can have the additional numbers and simplicity is important for my intake people. So I didn't spend the time. I've actually moved on to the problem that if I get the phone number for a session variable from a component that uses the mask for display (preferable but not crucial) the variable has the formatting. I am confident that I can solve this one but if you wanted to jot something down - you know, for everyone else - that would be fine.

you should be able to do via the db itself.
what database backened you are using?

MYSQL

Thanks again gandhi.

[sshutsell]

Re: Unformat display mask before saving phone number

This is semi-off subject, I was happy to learn about the TRANSFORM and REMSPECIAL here and was wondering how you were invoking the TRANSFORM you were formatting the phone number for the detail view. I have a program where I am doing this in a ajax callback but it seems to interfere with the client side formatting using the mask for US phone number. Entering a new number works great, however if you modify a phone number you have to enter the whole number from where ever you start the modification. For instance if the original number is (555) 123-4567 and you want to change to (555) 129-4567, you place the cursor to the right of the 3 and backspace, then you must enter 9-4567, not just the 9, it appears to be in overstrike vs insert mode.

Is this just the "normal" action or is there a way to get this to work as I would like it to work?