Check a webCRM sync before you run it

A sync from webCRM writes into records people are working on, so it is worth looking first. A dry run reads from webCRM and does everything a sync does except save.

Run a dry run

1. 1Open the webCRM integration and go to its sync tab.
2. 2Tick the types you want and set how many records to read per type.
3. 3Press Dry run.

Nothing is saved, whatever the result. The report underneath lists every record it read and what a sync would do with it.

See every field and value

Felter en synkronisering ville skrive shows each field across everything the run read: how many records have a value, how many would change, and an example. Use it when the point of a sync is one or two specific fields.

To look at one record, press the number in the Felter column. For a record you already have, you see Nå beside Etter synkronisering, with Bare det som endres on to begin with. A new record lists every value it would arrive with.

A field webCRM has no value for is not listed on a record you already have, because a sync leaves yours as it is. Two things a sync brings are not shown: quote lines, and the OBS line that becomes a company's flag.

See what a sync would refuse

A dry run also checks each record against the rules a real sync has to pass, so you hear about a failure before anything is written:

• A required field that webCRM has no value for.
• A value that is too long, not a number or a date, too large, or not one of the options the field allows.
• An offer number another deal already has, or a support case that already has an unlinked ticket.
• A link to a record that has since been deleted in DealJourney.

Ville feilet ({{count}}) in the row list shows those records, and pressing a record's number shows what is wrong with it. They are left out of the would-create and would-update counts, because a sync would not save them. If so many fail that a real sync would give up part way, the report says where.

When the check could not finish, the report says so instead of showing a clean result, so run it again before trusting it. Most rules are found this way, but not all: a sync can still fail on something no rule predicts, such as a connection dropping, and it does not look at quote lines.

Update only the records you already have

Turn on Oppdater kun eksisterende poster when you want to enrich what is already in DealJourney without bringing in anything new. A dry run and a sync then both follow the same rule:

• A webCRM record that matches one of yours updates it. A match is the link from an earlier sync, or the same matching a normal sync uses, such as the organisation number or the email address.
• A webCRM record that matches nothing is left out. It is listed as Utelatt and counted in the result, so you can see what stayed behind.
• No new fields, objects or timeline entries from the webCRM history are added. Timeline entries wait for the next ordinary sync, so nothing is lost.

A company's notes in webCRM are part of that company, so they still land on its timeline. A deal moved to a pipeline stage you do not have yet also gets that stage, or the deal would fall off the board.

The setting is remembered for the workspace. It applies to the dry run and to the sync on this page only. While it is on, Quick import is switched off, because that button brings in the whole account. The automatic hourly updates keep bringing in new records: to stop them, see Pause the automatic webCRM updates.