Contact: Title field is completely misleading

When the Contact ‘Title’ field is used in a Blueprint form or a correspondence template, the data is actually being pulled from the Organization ‘Employee’ affiliation record (unlike other Contact fields)!?!

So, the name of this field is totally misleading and confusing. Also, if you do not happen to use the Organization ‘Employee’ affiliation role then the field will just be blank.

Please can the logic behind this be reassessed or at least rename the field/display a warning when the field is being selected?

  • Guest
  • Mar 29 2023
  • Reviewed: Voting Open
  • Attach files
  • Deena Lauver Scotti commented
    June 05, 2023 18:03

    In general, the Contact/Affiliation title situation is confusing. You have to remember to put the title in the Affiliation record separately.

  • Jessica Tudyk commented
    April 03, 2023 16:19

    I concur! I pulled "Request: Primary Contact Title" as a column in a view assuming I was pulling the Request Record's Primary Contact's Title as you put in the pop-out that comes out on the right-hand side when you click the "Contact" of a request. I was confused when I realized those title's didn't match what was there. The fact that the "Request: Primary Contact Title" actually comes from an affiliation on the Organization record (instead of the request record) is crazy. AND the fact that the title comes from the "Employee" affiliation and not even the Primary Contact affiliation for the organization is even more ridiculous. I think the field title needs changed! But yes, at the very least a warning that what you think it should be pulling based on what it is named is actually not at all what you are pulling.