Config of personaccount

[skrissi]

Is there someone that configured the personaccount with this connector?
All times I'm received that the account record type is b2c business account

thank you

[olegforce]

@skrissi

• what value have you used under SF_SCRATCHORGPROFILE configuration in our .env file when you installed the solution?
• is Person Accounts enabled on the target org?

[skrissi]

Yes of course I wrote personAcocunts in env and yes it's enabled

[olegforce]

Hi @skrissi, if your .env file has SF_SCRATCHORGPROFILE=personAcocunts that would be the root cause, as the proper key/value pair per solution installation steps is SF_SCRATCHORGPROFILE=personaccounts. Could you please check that, and if the value is personaccounts, can you please validate deployed data, did the solution deploy person accounts matching rules or business accounts?
p.s. asking all of this, as it's working for everyone else, and I assume your issue root cause is not correct configuration during installation.

[skrissi]

ok @olegforce I will check can u say me if only the custumer its create in sfdc or order too?

[olegforce]

ok @olegforce I will check can u say me if only the custumer its create in sfdc or order too?

b2c-crm-sync solution doesn't sync order data. Its primary goal is to enable customer sync functions. With that related to the order, the use-case is only to sync customer data when an order is placed, if this feature is enabled after installations.

If you need to sync order data, you either should look into the Salesforce Order Management product and native connector that comes with it, or build order data sync functionality yourself.

[olegforce]

@skrissi I've seen a similar issue just recently reported by @nek4life under #107. You may wish to comment there, as it could be either regression in the solution or misconfiguration by you and @nek4life during the installation process.

FYI @ericszulc @jbachelet @sandragolden

[nek4life]

This was my configuration

## Salesforce Platform Configuration Properties
######################################################################
SF_SCRATCHORGPROFILE=personaccounts
SF_SCRATCHORGALIAS=crmsync
SF_SCRATCHORGSETDEFAULT=true
SF_SCRATCHORGFORCEOVERWRITE=false
SF_SCRATCHORGDURATIONDAYS=14

From the docs the only required field to enable personaccounts is the

SF_SCRATCHORGPROFILE=personaccounts

We are also seeing the wrong type of accounts being created. I opened #107 reporting this issue. I had thought I would see PersonAccount objects and not Consumer Direct Account and Contact objects separately. I did see both base and personaccount metadata deploy.

[nek4life]

@skrissi did you find a solution for this? We still have the same behavior as newly created accounts in Service are not showing up as PersonAccount records. I've verified our contact model is set to Person and also tried changing the default record type to our only other account record type and that did not solve the issue.

Existing Accounts show up as person accounts.

Accounts created through the connector show up as normal accounts

Our contact model is set to person

[skrissi]

Still not actually I still have the issue Le mer. 2 févr. 2022 à 16:32, Charlie Choiniere ***@***.***> a écrit :

…

@skrissi <https://github.com/skrissi> did you find a solution for this? We still have the same behavior as newly created accounts in Service are not showing up as PersonAccount records. I've verified our contact model is set to Person and also tried changing the default record type to our only other account record type and that did not solve the issue. Existing Accounts show up as person accounts. [image: Screen Shot 2022-01-28 at 11 46 46 AM] <https://user-images.githubusercontent.com/16930/152173471-6807603e-106d-4395-a1f5-e1397cf0755d.png> Accounts created through the connector show up as normal accounts [image: Screen Shot 2022-01-28 at 11 47 00 AM] <https://user-images.githubusercontent.com/16930/152173430-6daee270-328c-49f0-9a4b-1f8db9437203.png> Our contact model is set to person [image: Screen Shot 2022-02-02 at 9 31 29 AM] <https://user-images.githubusercontent.com/16930/152173759-57b7b5a5-8774-4e65-91f0-9386e88ce7ae.png> — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXAAUIXNXQDLMB4P22UK3RTUZE6AJANCNFSM5MU6FXFA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: <SalesforceCommerceCloud/b2c-crm-sync/repo-discussions/103/comments/2096395 @github.com>

[ericszulc]

Hi @skrissi , your account model is marked is Person, but is that record type in 'Account RecordType Developer Name' a recordtype where IsPersonType = true?

[nek4life]

I think I found the issue the flow that creates person accounts.

Instead of creating a Person Account record first, what the flow does is create a standard account and then it updates the account record type to a RecordTypeDeveloperName of 'PersonAccount' which is a hardcoded value. Normally you would create a PersonAccount first and Salesforce automatically creates a contact for you. I suspect it was developed this way to support both standard and person accounts.

The issue is that the Standard Account Record Type Developer Name is configurable, where the Person Account Record Type Developer Name is not and is a hardcoded value in the flow. In our Org, the value for this is not PersonAccount so this causes a silent error to occur and the record is never updated and thus not changed to a person account.

See the B2C Commerce: Process: Create Or Update Contact flow and navigate to the following Get Records node

You can see the value here is hard coded to 'PersonAccount' so in our case no record type is actually found. We updated this to the id of our actual person account record type and the flow started working correctly.

The value for your org's record type can be found here through Object Manager.

There should be an additional setting for personaccounts like this value for standard accounts found here

I do not know what else is hardcoded to this value, however, it makes sense to me that if this value is configurable for standard accounts it should be configurable for person accounts as well to maintain upstream compatibility with the framework instead of having to change hardcoded values.

@jbachelet @olegforce @ericszulc do you know of any other areas this might be a problem? I suspect it could cause additional errors.

Thanks,
Charlie

[ericszulc]

@nek4life that's an amazing catch. yes, it was setup like that to minimize the variation between person and standard accounts. I don't think there is any other spots it would be hard-coded, but a quick search through all the metadata should tell you that quickly.

[skrissi]

I don't understand what I need to do @nek4life

[skrissi]

I don't see the phone number in the contact after synchronization @jbachelet @olegforce @ericszulc
Where i need to check this issue

[jbachelet]

The phone is mapped based on the current Custom Metadata Integration Mapping provided by b2c-crm-sync out of the box.
Please go to Setup > Custom Metadata > B2C CRM Integration Mappings to see them.
You can edit these settings to map the phone to the correct field in b2c if you are not using the standard ones.

[jbachelet]

Hello @skrissi ,

I just opened a PR(#114) to fix this issue.
Can you please checkout this branch and deploy it to your org and test this scenario?

Thanks!