Announcement

Collapse

Information Needed

See more
See less

C&P Settings Custom Mapping Visualforce Error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • C&P Settings Custom Mapping Visualforce Error

    Hello, I would like to update the Custom Mapping of Suffix from a custom field to the native Salesforce field. However, when I go to the Custom Mapping page, I get this error message:

    Map key Suffix__c not found in map
    Error is in expression '{!fieldlistmap_8[cq.Object_Map__c][cq.Field_Map__c]}' in component <apex:repeat> in page cnp_paas:cnp_settings_custom_question

    Any advice? I took a look at the Visualforce page but I'm not sure exactly what to change with the code. I have also granted C&P Customer Support access to my org.

  • #2
    Good day @abenes

    We fixed it for you.

    You had a field "Suffix" that was first mapped in the C&P Settings and later deleted. C&P Settings could not find the record and as such was generating the error.

    We deleted the field from the settings area manually so it works now.

    Test it and let us know.
    Regards,
    Click & Pledge Support Department

    On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #3
      I am able to access the page now. However, why is the native Salesforce "Suffix" field unable to be chosen from the field map picklist?

      Comment


      • #4
        If I'm able to map the native Suffix field, can you also tell me where I can find the FieldName (i.e. FieldName2603) and FieldValue (i.e. FieldValue2603) codes for the Visualforce page?

        Comment


        • #5
          Suffix is included as part of a "combination field" to create the native Salesforce field 'Name'. If you look at Setup > Contacts > Fields, you'll see this:

          Click image for larger version

Name:	2019-10-24_FRM_Cara png.jpg
Views:	32
Size:	21.0 KB
ID:	49578


          Note the 2nd column starts with 'Name' which is the actual API name of the native Salesforce field. Salesforce creates an automation that combines the values of the 5 fields listed to create the Name field.

          Our Custom Mapping includes all fields that represent standard data types: text, picklist, boolean (true/false)..., but this name field is a unique format. There are other fields that have unique formats that are not available in Custom Mapping, for example:
          • lookups (the data displayed is usually the name of the record, but the data that salesforce is actually storing is the Id)
          • email fields
          • URL fields
          • Phone fields

          Salesforce has these extra 'field types' so that they can force intrinsic validation- email addresses must have '@' and "."xxx, etc.

          Programmatically, if you were to have those fields available, and you entered a text value that failed the Salesforce validation, you'd get an error. Salutation is available because you can set the values in the field properties, but note that you don't have the ability to do much to the other Name 'fields'.

          Hope that makes sense. I would recommend you map to "Professional Suffix" instead.

          Here's some references about how other users have managed this issue:
          Regards,
          Click & Pledge Support Department

          On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

          Join us @ the educational webinars: https://clickandpledge.com/webinars/
          Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
          Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

          Comment


          • #6
            Thank you for the detailed explanation! I did end up mapping to Professional Suffix, and then created a Workflow Rule to route the value to Suffix.

            Best,
            Alison

            Comment

            Working...
            X