Having Google'd a LOT, I believe the problem is there because the isPersonAccount boolean field is not set at the point of creating the account (in VF) and therefore the page does not allow the name fields to render. That's obviously no correct as they work fine in edit mode (having created a person account using the standard page) and they are also listed in the WSDL file. Having spoken to Salesforce about this (as this is quite a fundamental issue), they claim the those 3 fields have no API field definitions and so cannot be called via a VF page. BUT, when creating a NEW Person Account, the Salutation, First Name and Last Name field so not show on the page and so the record cannot be saved (as Last Name is required to create an account). Now, when editing accounts, everything works currently, all fields show and PA works fine. To resolve this, I have created a Visualforce page that covers all account record types, including Person Accounts and have overridden the 'new' and 'edit' buttons to call the VF page.
To integrate PA in the console, it has to be done via a visualforce page as there is no sidebar to load the app.
We will be using these within the service console and also integrating Postcode Anywhere for address lookups. I have recently activated and configured Person Accounts in our salesforce org.
0 kommentar(er)
