Optional Address & Street 2 in V11 Migration

Hello all,

I see that the 'Opt. Address' value in v10 is now 'Street 2' in v11. My org has used 'Opt. Address' for business names that needed to be in the postal address. That made sense when the business name was above the Street Address, but is now confusing when moved below.

I know that in T_DEFAULTS you can change the order of Street 1/2/3, but I am hesitant to create a potentially confusing view to the operator where Street 2 is above Street 1.

I am assuming that you cannot rename Street 2 to 'Business Name' or back to 'Optional Address'?

Has anyone else changed the order of the Street  and had good experiences, or found some interesting results to share?

Best,

Nicholas

Parents
  • Former Member
    Former Member $organization

    Hi Nicholas

    We have a different change in place to hold business names.

    We discovered that there is a magical code to use in the TR_SALUTATION_FORMAT table, which locks the value against being updated by the GenSal function. It's mentioned in the Help, but you have to read very carefully to see it. Luckily Kim Lee has eagle eyes.

    If you put just an exclamation mark in the format field, that means 'Manual entry only", effectively, and locks the value to whatever is entered manually, protecting it from the dreaded Gen Sal.

    So what we did was

    • rename the Salutation 2 textbox as "Organisation", and 
    • put a "!" in all of the individual Single Name L2 format fields in TR_SALUTATION_FORMAT. 

    That gives us a Business Name field, effectively, although we had to sacrifice the L2 salutations - nobody in the UCSS consortium had a problem with that, but other orgs might feel differently.

    You also have to enable the LSal2 field to be included in label salutations, in T_DEFAULTS, to make it editable..via this setting below...

    LABEL USE ESAL2

    The default action of the system is to ignore the Salutation 2 field when generating label salutations, which also locks this field for editing on the General tab if the default salutation is a label salutation. Changing the default value to Yes causes the second salutation field to be included when generating salutations and makes the field editable on the General tab.

     

    Ken

     

  • Thanks Ken, I will share that with our key CRM users, very nice.

    I feel we will stick with renaming and moving Street 2 as this won't involve any aditional data mapping, but Salutation 2 will come in handy in the future I am sure, currently we have that made inactive.

     

Reply Children
No Data