astro46
Senior Member
- OS Version(s)
- Windows
- Outlook version
- Outlook 2021 64 bit
- Email Account
- IMAP
I have had a problem using a custom form in outlook 2013, email, address, phone fields do not display with correct field names. i posted about this in the microsoft social forum, originally thinking that it was only a problem with seeing email "display name" field, but have since found that the problem is more fundamental than that. the only reply that i have received there was from a user indicating the same problem with a custom email form. since posting there i have come up with more information:
as an experiment I rolled system back to just after uninstalling Office 2010, then deleted whatever office files and folders i could find in appdata, except for some of the templates (though i deleted any outlook templates), changed the mail>data file location . and opened outlook.
when i created a new contact, of course it gave me the native contact form. it is titled 'untitled- contact (design)' ok. then i opened developer>design a form and picked the contact form from standard library. (picking it from 'contact' gives the same result). a form opened that looked very much like my custom form. apparently design always change to this format, since i saw the same change in ol10. the notes field is across bottom of form, and no business card field. BUT, in OL13 design mode fields are misnamed. the top phone field is called 'email3'. email field is called 'other'. similar to how it is messed up in my custom contact form.
clicking 'run this form' , if no changes were made to the initial design form, takes you back to the native contact form format, with notes on right, with business card. fields correctly named. changing fields from drop down boxes, gives the fields picked.
however if anything is changed on the design form, and then click 'run this form' the format stays like the design form format (not the native form), fields stay incorrectly named, picking a field from drop down list gives a different field from one picked. notes field remains along bottom, no business card.
so, 'design a form' is basically the custom form design that i use with a few fields added or resized. but ol13 screws up the field names in the design form, and retains those mistakes if any change is made to the native form. and seems to force this corruption on a customized form in normal use.
this should be easily reproducible .
as an experiment I rolled system back to just after uninstalling Office 2010, then deleted whatever office files and folders i could find in appdata, except for some of the templates (though i deleted any outlook templates), changed the mail>data file location . and opened outlook.
when i created a new contact, of course it gave me the native contact form. it is titled 'untitled- contact (design)' ok. then i opened developer>design a form and picked the contact form from standard library. (picking it from 'contact' gives the same result). a form opened that looked very much like my custom form. apparently design always change to this format, since i saw the same change in ol10. the notes field is across bottom of form, and no business card field. BUT, in OL13 design mode fields are misnamed. the top phone field is called 'email3'. email field is called 'other'. similar to how it is messed up in my custom contact form.
clicking 'run this form' , if no changes were made to the initial design form, takes you back to the native contact form format, with notes on right, with business card. fields correctly named. changing fields from drop down boxes, gives the fields picked.
however if anything is changed on the design form, and then click 'run this form' the format stays like the design form format (not the native form), fields stay incorrectly named, picking a field from drop down list gives a different field from one picked. notes field remains along bottom, no business card.
so, 'design a form' is basically the custom form design that i use with a few fields added or resized. but ol13 screws up the field names in the design form, and retains those mistakes if any change is made to the native form. and seems to force this corruption on a customized form in normal use.
this should be easily reproducible .