Keep your data up-to-date

Like all of our integrations, you can keep your data up-to-date the moment a change occurs. This is done using our Monitoring services. For Dynamics CRM, we allow you to choose between two ways of getting your updates; direct update of the data, or notifications about updates that can then be reacted to however you see fit.

Option 1: Field updates

This is the default offering we have for any integration; map your fields in CRM to fields from Lasso and put a checkmark in 'Opdater felter', and we will make sure those fields are kept up-to-date with the newest information. No code or setup in Dynamics 365 required, all is handled from within Lasso.

Option 2: Receive update notifications

We also offer a more customizable solution; having updates sent as metadata. That is, once an update occurs, we will create and relate a new object (a 'Firmaopdatering') to the monitored entity in Dynamics 365, which contains the types of changes that have occurred, such as 'Regnskab', or 'Bestyrelsesændring'. The idea is then that you can use the Dynamics 365 Platform to react to the creation of those entities, e.g. by retrieving the data from Lasso and updating the fields you require, notifying relevant people, or whatever you desire.

To get the required objects (ie. 'Firmaopdatering') for Dynamics 365, visit the download page at DynamicsCRM.dk. You will currently need the 'Workflow Plugins' solution file in order for Lasso to create 'Firmaopdateringer'. This solution also contains workflow plugins to fetch data from Lasso, though we suggest using our Power Automate Connector for your implementation instead, as it is what is currently recommended by Microsoft, and because it supports a wider range of data to be fetched from Lasso.

Best of both worlds

Note that these options are not mutually exclusive; you can have your fields updated directly, while receiving notifications about the changes that have occurred at the same time.

Types of notifications

When a 'Firmaopdatering' is created and associated with an entity, the type of update is recorded in the "Type" field. This is a text field, containing a string representing the update, e.g. "Status" for status-changes, "Antal ansatte" for change in the number of employees and so forth. If multiple updates are registrered at the same time, the types will be separated by a pipe |.

Keeping it simple?

Please note that "Staminformation" is a catch-all for most basic information changes, which means you can just watch out for this type if you want to react to any of them in the same way. It is present whenever any of the following updates happen: Adresse, Binavn, Bibranche, Branche, Fax, Formål, Email, Navn, Selskabskapital, Tegningsregler, Telefon, Virksomhedsform, Website

The full list of types of updates is listed in the below table:

Types of Firmaopdateringer

Adresse
Anden reel ejerskabsændring
Antal ansatte
Årsrapport
Bestyrelsesændring
Bibranche
Binavn
Branche
Deltagerændring
Direktionsændring
Ejerskab af virksomhedsejendom påbegyndt
Ejerskabsændring
Email
Fax
Fjernet fra overvågelse
Formål
Fusion
Gentag forsøg
Going concern
Kontaktperson fjernet fra hjemmeside.
Kontaktperson(er) fundet på hjemmeside.
Kontaktpersoner fra hjemmeside opdateret
Livsforløb afsluttet
Livsforløb startet
Manuel opdatering
Navn
Ny besked fra Statstidende
Ny historie
Ny Paqle artikel
Ny pressemeddelelse
Nyt datterselskab
Nyt firma
Nyt telefonnummer
Overvågningshandling
PEnhedFjernet:{PNUMMER}
PEnhedOpdateret:{PNUMMER}
PEnhedTilføjet
Potentiel overvågnings match
Prospect fundet
Prospecting tidspunkt nået
Reel ejerskab
Reel stemmeandel
Reklamebeskyttet
Revision
Selskabskapital
Sidst opdateret
Søgedatabase opdateringskandidat
Søgedatabasen blev opdateret
Staminformation
Status
Tegningsregler
Teknologier fra hjemmeside opdateret
Telefon
Tilføjet til overvågning
Ukendt
Ultimativ ejerskab
Vedtægter
Virksomheden startede som ejendomsadministrator
Virksomheden stoppede som ejendomsadministrator
Virksomhedens autorisationer ændret
Virksomhedens ejendomsbesiddelse ophørte
Virksomhedens ejendomsejerskabsændring tilbagerullet
Virksomhedsform
Website
Ændring af ejendomsejerskab

Reacting to an update notification

Here's the steps on how you can create a flow in which your CRM system will automatically respond to an update notification. Before following this guide, it is important to note that the CVR has to be present on the entity, in order to look up the company in Lasso.

Creating the trigger

1. Visit https://make.powerautomate.com/ and click Create.
2. Click Automated cloud flow and search for "dataverse" for the trigger. From here, choose "When a row is added, modified or deleted", finally press Create.
3. In Change type, select for it to trigger upon creation.
4. For Table name select "Firmaopdateringer".
5. Select "Organization" as your Scope and click + New step.

Fetching the entity to update

1. Select "Get a row by ID" in the Microsoft Dataverse connector.
2. Choose Accounts as your Table name.
3. Choose Associated(Value) as your Row ID and click + New step.

Getting company data from Lasso

1. Select "Lasso X" in the list of premium connectors, and depending on your needs, select the appropriate action, e.g. "Get company information".
2. Fill in the field that the Lasso X connector requires. You can choose this dynamically by simply selecting it from the list of dynamic content. Typically this will you use for CVR. Now click + New step.

Creating an action

1. Finally, choose the action that should occur when this flow is triggered, and fill out the required fields. For this, you will have the Lasso X data available to you. If you wish to update the row that got an update notification, simply fill in the fields Table name and Row ID, where Table name is either "Accounts" or "Leads", and Row ID, is an id to be found in Dynamic content as either "Account" or "Lead". Then choose the fields you want to update.
2. Test your flow in the top right and fix any potential errors before pressing Save.

If done correctly, you will end up with a flow looking approximately as such:

Testing update notifications

You might find it necessary to test the update notifications, without having to wait for an actual update to occur. To do this, trigger an update by calling a specific endpoint:

POST https://api.lassox.com/integrations/dynamicscrm/test/push?lassoId=CVR-1-34580820&message=test&accesskey={API_KEY}

Make sure the provided lassoId is being monitored by Lasso, so that Lasso can find the corresponding entity in Dynamics 365. Also make sure to use the correct API key.

This will create a an Update notification (Firmaopdatering) in Dynamics 365 with the provided message as Type.

Required privileges

For Lasso to write back to Dynamics 365 — whether creating the Firmaopdatering update notifications described above, updating fields directly, or creating new records — the user account Lasso connects with needs a security role with the privileges below. Each cell shows the minimum access level required for that privilege; a dash (—) means no privilege is needed for that combination.

The privilege names are the standard Dynamics 365 ones — Create (Opret), Read (Læs), Write (Skriv), Append (Tilføj) and Append To (Føj til) — and the access levels map to the security-role editor as follows:

Access level	Danish	Meaning
Organization	Organisation	Across the entire organization.
Business Unit	Afdeling	Within the user's own business unit.
User	Bruger	The user's own records only.

Required to push updates

Entity	Create	Read	Append	Append To
Account (Firma)	—	—	—	Business Unit
Lead (Kundeemne)	—	—	—	Business Unit
Customer relation (Kunderelation)	—	—	—	Business Unit
Company update (Firmaopdatering)	Organization	Organization	Organization	—
Contact update (Kontaktopdatering)	Organization	Organization	Organization	—
Lead update (Kundeemneopdatering)	Organization	Organization	Organization	—

The Append To privilege on Account, Lead and Customer relation is what lets Lasso relate a created update object (the Ansvarlig/owner reference) to the monitored record.

Required to update records

Entity	Create	Read	Write
Account (Firma)	User	Business Unit	Business Unit
Lead (Kundeemne)	User	Business Unit	Business Unit
Contact (Kontaktperson)	User	Business Unit	Business Unit

Required to create records

Entity	Create	Read	Write	Append	Append To
Account (Firma)	Business Unit	Business Unit	Business Unit	Business Unit	Business Unit
Lead (Kundeemne)	Business Unit	Business Unit	Business Unit	Business Unit	—
Contact (Kontaktperson)	Business Unit	Business Unit	Business Unit	User	User
User (Bruger)	—	Business Unit	—	—	—
Marketing list (Marketingliste)	—	Business Unit	—	—	Business Unit
Field (Felt)	—	Organization	—	—	—
Entity (Objekt)	—	Organization	—	—	—
Relationship (Relation)	—	Organization	—	—	—