The data updater provides a way for Business Improvement Districts to synchronise the content of their Solomon database with non-domestic rates data (NNDR) provided by their local authority partner.

During the first step of the updater process, Solomon iterates over each row of data the council provides, and tries to find a matching record in Solomon using a property reference number and a combination of billing reference and liable party name. 

Based on what Solomon finds, users are presented with a series of decisions to make.
Decisions are grouped into three main types, and each type has a specific set of actions, as follows:

Create

Rationale: 

Solomon was unable to find a record in its database that matched the council row using the property reference number. By default, Solomon assumes that this is a new hereditament and intends to create a new Business record.

Actions: 

  • Create: you choose to create a new Business record in Solomon using data from the council row (default.)
  • Match: you choose to find an existing record from Solomon to update using the council data. You can only choose from inactive database records, or records that have been flagged for archiving (see the Archive section below.) You should use this if a Business has moved and you want to carry People and Activities to the new hereditament, or if the new hereditament is the result of an old one splitting, and you want to carry an existing record over.
  • Ignore: you choose to ignore the council row completely. You should use this if the hereditament is outside of the BID area, for example.

Replace

Rationale: 

Solomon was able to find a record in its database that matched the council row on property reference, but couldn't match on billing reference (or on liable party name, if your council changes billing references regularly and you have asked for us to check the name too.) By default, Solomon assumes that the existing record in Solomon should be marked as inactive, and a new Business created from the council row.

Actions: 

  • Replace: you choose to make the existing Solomon record inactive and create a new Business from the council row (default.)
  • Update: you choose not to archive the existing record and to update it using the council row instead. 

Archive

Rationale:

Solomon was unable to find a matching record from its database in the council's data, based on property reference. By default, Solomon assumes that this hereditament has left the BID area and the related Business is to be marked as inactive.

Actions:

  • Archive: you chose to mark the record in Solomon as inactive. It will remain in the database but will not be returned unless the user specifically asks to see inactive records.
  • Ignore: you chose to ignore Solomon's recommendation and the record remains active in the database.

Please use live chat to ask our team for help with the data updater, or to arrange a training session.

Did this answer your question?