Skip to main content
If something isn’t working in Accounts and Contacts, find the symptom below.

​
Address Flow Down

What you see. You edit the Billing Address on an Account that has several related Contacts, save, and the Contacts’ Mailing Addresses still show the previous address.Why. When an Account has many related Contacts, fusionCore updates them in the background rather than the instant you save. The Contact addresses catch up a moment later.Fix. Wait a short while, then refresh the Contact to see the updated Mailing Address. If a specific Contact never updates, it most likely has its own different address — automatic flow down leaves those untouched. Use the Sync Address Details button on that Contact to overwrite it on demand. See Account Address Flow Down.
What you see. You add a Contact under an Account, save, and the Contact’s Mailing Address is still blank instead of matching the Account’s Billing Address.Why. Automatic flow down only runs when three things are true: the Account’s Billing Address is filled in, Allow Address Flowdown is checked on the Account, and the new Contact’s Mailing Address was left blank. If any one of these is missing, the address is not copied.Fix. Open the Account, confirm the Billing Address is populated and Allow Address Flowdown is checked, then either recreate the Contact with a blank Mailing Address or use the Sync Address Details button to copy the address on demand. See Account Address Flow Down.
What you see. You clicked Sync Address Details and the Contact’s existing Mailing Address was replaced with the Account’s Billing Address, even though the Contact had its own different address.Why. The manual button is not conditional. Unlike automatic flow down — which only fills a blank address or updates one that still matched the Account’s previous address — the button always overwrites the Mailing Address with the Account’s Billing Address. On an Account it does this for every related Contact at once.Fix. Re-enter the address the Contact should have. To avoid this, use the button only when you actually want the Account’s address copied down. For Contacts that need their own address, rely on automatic flow down instead, which leaves their address alone. See Account Address Flow Down.
What you see. The Sync Address Details button is missing from the Account or Contact record, or clicking it does nothing.Why. The button only appears if your administrator has added it to the page layout, and you need the address-flow-down permission set to use it.Fix. Ask your administrator to add the Sync Address Details button to the Account and Contact page layouts and to grant you the permission set. If the button is present but hidden, click the dropdown arrow (▾) next to the other action buttons to reveal it. See Account Address Flow Down.
What you see. Flow down updated the standard Mailing Address, but custom address fields you added stayed empty.Why. Flow down copies only the standard Billing address fields into the standard Mailing address fields. Custom fields are not part of the copy.Fix. Update any custom address fields yourself. See Account Address Flow Down.

​
Person Accounts

What you see. You create a Person Account with a Billing Address but no Mailing Address, save, and the Mailing Address stays empty — even with Allow Address Flowdown checked.Why. Automatic flow down copies an Account’s address down to its related Contacts, and a Person Account has no separate child Contact to copy to. Saving a new Person Account does not fill its Mailing Address from the Billing Address today.Fix. After you save, click the Sync Address Details button on the Person Account to copy the Billing Address into the Mailing Address. See Using Account Address Flowdown with Person Accounts.
What you see. On records tied to a Person Account, the customer name appears empty or shows the wrong value.Why. fusionCore resolves the individual through its own current customer fields. If the older fields are still on the page layout instead of the current ones, the name can read blank or incorrect for Person Accounts.Fix. Ask your administrator to add the current fusionCore customer fields to the Order, Credit, and Purchase Activity page layouts in place of the older fields. See Person Account Support.
What you see. You create a Person Account, then try to create a Contact and link it to that Person Account, but the Person Account does not appear in the search.Why. A Person Account already combines an organization and a person in one record, so it does not take separate child Contacts. There is nothing to attach a Contact to.Fix. You don’t need to add a Contact — the person’s details already live on the Person Account itself. Use the Person Account record directly. See Person Account Support.
What you see. Person Accounts are on and you want to remove the feature, but there is no option to disable it.Why. Enabling Person Accounts is a permanent Salesforce change. Once on, it cannot be turned off.Fix. There is no way to reverse this. Plan carefully before enabling it in a new org, and review the readiness check and org impacts first. See Enable Person Accounts.

​
Communities

What you see. You create a Community Member and get an error on save, often when the member was created without a Community Type.Why. A member’s role depends on the Community’s Type. When the Type is blank, the role can’t be assigned, and the save fails.Fix. Add the member from the Community Members related list on the Community record rather than the standalone New button. Adding it from the Community fills in the Community Type automatically, so the role can be assigned. See Community Member.
What you see. The Role picklist on a Community Position doesn’t show the value you expect, or you get an error when you save a position after adding a new role value.Why. The available Role values depend on the Community’s Type. If a role value isn’t part of the Type’s set, it won’t appear; and if your set of roles doesn’t include Member, creating a position can fail.Fix. Set the correct Type on the Community first, and make sure Member is one of the roles available for that Type. Then the role you want will appear and the position will save. See Community Position.
What you see. As an administrator you change the Community Type on a member or position, but after saving it reverts to the Type on the Community.Why. The Community Type is meant to come from the Community and be read-only on members and positions. Administrator profiles can edit fields that are read-only for everyone else, which makes the field look editable when it isn’t meant to be changed there.Fix. Set the Type on the Community itself, and let it flow down to members and positions. Day-to-day users on a standard profile see the field as read-only, which is expected. See Communities.
What you see. A Community Member record exists but has no person on it.Why. Community is required when you create a member, but Contact is not. It’s possible to save a member with the Contact left blank, leaving an empty membership.Fix. Always fill in Contact before you save. Open the empty member, add the Contact, and save. See Community Member.
What you see. You set Status to Active, Future, or Expired by hand, but it doesn’t keep your value.Why. Status is calculated automatically from the Start Date and End Date. Editing it directly has no effect.Fix. Change the dates to change the status. For example, a member whose dates are both in the future shows as Future. See Community Member.
What you see. You try to delete a Community and Salesforce blocks it.Why. A Community can’t be deleted while it still has members attached.Fix. Remove or end the Community’s members first, then delete the Community. See Communities.

​
Accounts and Contacts

What you see. You start an Order from an Account but can’t add products or line items.Why. An Order needs a Bill To Contact before you can add line items, and fusionCore fills the Bill To Contact from the Account’s Billing Contact. If the Billing Contact is blank, the Order has no one to bill.Fix. Set the Billing Contact on the Account so it carries onto new Orders, or set the Bill To Contact directly on the Order before adding line items. See Accounts.
What you see. A Contact exists, but fusionCore won’t create an Order for that person.Why. Order automation requires an Account. A Contact that isn’t linked to an Account has nothing for the Order to attach to.Fix. Associate the Contact with an Account, then create the Order. See Contacts.
What you see. You edit a field such as Organization Membership, Original Join Date, or Membership End Date, save, and your value is replaced.Why. These membership, join-date, and credit fields are populated by automation. fusionCore overwrites a value you type in with the value it calculates.Fix. Don’t edit these fields by hand — let the automation maintain them. If a credit total looks out of date right after a change, refresh the record a moment later, because it’s calculated rather than a live total. See Accounts and Contacts.