Choose how each field syncs with your PSA
Decide, field by field, whether your PSA keeps updating a value or BeeCastle keeps your edit.
Purpose
Choose, field by field, whether your PSA keeps updating a value or BeeCastle keeps your edit. For example, let your PSA fill in an opportunity's Expected close when the deal first arrives, then keep the date your team sets in BeeCastle, even after later syncs.
This works for every field your PSA fills in, built-in or custom, on companies, contacts and opportunities. Only owners and admins can change these settings.
The screenshots and video use ConnectWise Manage. It works the same way with Autotask and HaloPSA.
Fields your PSA owns
Open a company, contact or opportunity that came from your PSA and choose Edit. A field your PSA updates on every sync can be read but not changed, because the next sync would replace any change you made. Hover over it to see why.
A small arrow inside each field your PSA fills in shows which way it syncs: an arrow pointing left means the value comes from your PSA, an arrow pointing right means it goes to your PSA. Hover over the arrow to see the rule, for example From PSA, or From PSA, on create only. Click it to see the rule in full. Owners and admins can choose Edit field there to change it.
Records you created in BeeCastle, and that aren't linked to your PSA, can always be changed.
Change a field's sync rule
- Go to Settings, then Custom fields, and choose Companies, Contacts or Opportunities.
- The PSA column shows, for each field, the PSA field it is read from, which way the value travels, and when it may change.
- Open the field's menu and choose Edit. The PSA sync section is at the bottom.
- Choose a Direction and, under When the PSA sends a value, choose when an incoming value may replace yours.
- Choose Save changes.
Direction
| Direction | What it means |
|---|---|
| From your PSA (the default) | The sync reads the value. Edits in BeeCastle are not sent to your PSA. |
| Both ways | The sync reads the value, and edits in BeeCastle are sent to your PSA. |
| To your PSA | Edits in BeeCastle are sent to your PSA. The sync never reads the value. |
| Not synced | The field lives in BeeCastle only. On records from your PSA it stays empty, even when your PSA holds a value, until someone fills it in BeeCastle. |
When the PSA sends a value
This only applies when the direction brings values in (From your PSA, or Both ways).
| Choice | The sync writes the field |
|---|---|
| Always (the default) | On every sync. |
| On create only | Only when the record first arrives from your PSA. After that, the value is yours to change. |
| Only when empty | Only while the field is empty in BeeCastle. If you clear the field, the next sync fills it again. |
On create only means the record is created by the sync. If your PSA record is linked to a company or contact that already existed in BeeCastle, values set to On create only are not copied over; use Only when empty to fill in the gaps.
Edit a field your PSA fills in
Once a field is set to On create only or Only when empty, it opens for editing on records from your PSA. Change it and save as usual. The next sync leaves your value in place, while fields your PSA still owns are brought up to date.
Fields that always come from your PSA
Some fields can't change, and their choices are greyed out with the reason on hover:
- Fields that link a record to others, such as a contact's or opportunity's company, an opportunity's contact, and the date an opportunity was opened, always come from your PSA.
- Fields a record can't be created without, such as names and an opportunity's status, must come in from your PSA. They can't be set to To your PSA or Not synced.
- Some fields are set together with another field and follow its rule. Pipeline stage, source stage, source status and the closed date follow Status. Expected revenue follows Amount. Sales rep follows Owner. State, city and postcode follow Country, because they come from one address. These show Set with, followed by the field they follow.
Sending edits back to your PSA
Both ways and To your PSA are available for the opportunity fields BeeCastle can send: name, expected close, status, amount, probability and owner. They need all of the following:
- A PSA that takes edits from BeeCastle. ConnectWise Manage and Autotask do. HaloPSA does not yet.
- Opportunity editing turned on for your workspace. Contact BeeCastle if it isn't.
- Opportunities set to Both ways on your PSA integration's Entities tab (Settings, Integrations, your PSA).
ConnectWise Manage can't take a probability from BeeCastle, so Both ways and To PSA are greyed out for Probability.
Company, contact and custom field edits are never sent to your PSA.
If your workspace already sends opportunity edits to your PSA, those fields start on Both ways, Always, so nothing changes until you choose otherwise. An edit that hasn't reached your PSA yet is kept, and a sync won't put the older value back.
If sending later stops being possible (for example, opportunities are set to come in only), a field on Both ways acts as From your PSA, and a field on To your PSA acts as Not synced, until sending is possible again. Your choice is kept.
What happens when you change a rule
- Values already on your records stay as they are. Nothing is restored or overwritten when you save.
- When the change lets the sync write more (for example, back to Always, or from Not synced to From your PSA), BeeCastle asks your PSA for a full refresh of that record type, so your records catch up on the next sync.
- Every change is recorded with who made it.
Merged records
When you merge two records, the values you choose in the merge stay as chosen. A merge's choice for a field wins over the field's sync rule, until you set that field back to follow your PSA on the record.
Custom fields from your PSA
Custom fields you've connected to a PSA field (with Discover from PSA) have the same Direction and When the PSA sends a value settings, limited to From your PSA and Not synced. A custom field on From your PSA, Always can't be edited in BeeCastle, on any record; any other choice opens it for editing.
Was this article helpful?
Related articles
Integrating BeeCastle with ConnectWise Cloud
4 quick steps to sync BeeCastle with CW Cloud
ConnectWise IntegrationIntegrating BeeCastle with ConnectWise On-Premise
6 steps to sync BeeCastle with your CW on-premise server
ConnectWise IntegrationEmbed BeeCastle in ConnectWise
Please note: Currently only available for ConnectWise customers Available for all BeeCastle customers (including Prof...
ConnectWise IntegrationBeeCastle and ConnectWise Integration FAQs
Understanding the BeeCastle and ConnectWise integration