Tables extended from the Account table cannot be set as Contact Accounts

[HIROSHI SATOH]

I created a table that extends from the Accounts table.
I was unable to register the data from the extended table as an account in Contacts.

What do you think could be the cause? Thank you in advance.

[HIROSHI SATOH]

It seems I can't register due to the following business rule. This business rule cannot be changed. Is there a workaround?

This item is read-only based on its protection policy.

「Sync account to company」

function onBefore(current, previous) {
	current.company = current.account;
	if(current.account.sys_class_name != 'customer_account')
		current.account = '';
}

[HIROSHI SATOH · Accepted solution]

We have concluded that the accounts table should not be expanded.

[Wasif]

Though this thread is closed, just to put in my cents to it,

Though there's an out of the box BR, which is restricting your customization, but if there's a need (or customization) as is in your use case, you may create another onBefore BR, with a higher order which would run later and take final effect, and you may put in the association logic that tailors to your use case.

We were faced with a similar case, where this BR was a bottleneck.
We wanted to map the account's 'parent' field to the contact's 'company' field, which clearly isn't the out of the box logic listed in the BR, so we created another BR - 'Sync account to company_2' with order 200 (out of the box BR - 'Sync account to company' has order 100) and we wrote custom logic to map relevant field, and we were able to achieve our customization.

Food for thought!

[HIROSHI SATOH]

For now, following the out-of-the-box practices aligns best with our organization’s governance and facilitates more seamless collaboration between teams. Thanks again for your input and for providing best practices to consider!