Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Address fields for both Account and Contact won't accept new translations RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am working on a CRM 4.0 implementation that uses a bilingual French/English interface.  For all of the Address fields (Address 1, Address 2) in both Account and Contact we have modified the names slightly.  In all cases, the changes made in the translation file are being ignored for these fields for both entities.  We have translated terms in lots of other places and not had this issue.  It seems to be specific to those address fields.  I have cleared my cache and published the customizations many times and nothing seems to work.

    Has anyone experienced this issue?  Any ideas on how to resolve it?

     

    Thanks.

    Friday, December 17, 2010 10:45 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    Unconfirmed but my guess is the translation changes the attribute display name (set on the attribute). In most cases this flows down to the form. However, address fields are a bit special in that the name on the form (Street 1, for example) is different to that on the attribute (Address 1: Street 1).

    If this is the case, the solution is probably to change the form label back to the attribute display name and hopefully the translation will carry through.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog

    http://leontribe.blogspot.com/ 
    or hear me tweet http://www.twitter.com/leontribe

    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    Monday, December 27, 2010 4:59 AM

All replies

  • Question
    Sign in to vote
    2
    Sign in to vote

    Unconfirmed but my guess is the translation changes the attribute display name (set on the attribute). In most cases this flows down to the form. However, address fields are a bit special in that the name on the form (Street 1, for example) is different to that on the attribute (Address 1: Street 1).

    If this is the case, the solution is probably to change the form label back to the attribute display name and hopefully the translation will carry through.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog

    http://leontribe.blogspot.com/ 
    or hear me tweet http://www.twitter.com/leontribe

    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    Monday, December 27, 2010 4:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This actually did work.  Originally I only changed names on the form by changing an attribute's display name and letting it cascade.  For some reason (a  bug?), this causes those labels to be excluded from the translation file when exporting it.

    When I changed the label names (directly on the form) back to the default values and exported the translation file, lo and behold, they began showing up.  From there, I just had to edit both the English and French values to my preferred terminology, import, publish, and all is well.

    Thanks for getting me on the right path.

    Wednesday, January 5, 2011 9:11 PM