Configure the connection and identification fields
An administrator configures the connection so that Ferli names and addresses reach the correct cards. Have your Ferli credentials and, for file-based integration, Azure Function settings ready before starting.
Purpose
Choose between retrieving information for one kennitala through the web service and processing base and update files. Identification mapping applies to both customers and vendors.
Prerequisites
The Ferli extension and your Ferli account must be active. Ask Rue de Net to help set up the Azure Function for file-based integration. Do not use credentials from screenshots or documentation examples.
Permissions needed
The user needs permission to change setup and the cards being updated. Scheduled runs also require permission to run the job queue. An administrator assigns suitable permissions.
Steps
- Open National Register Setup through Business Central search.
- Choose Customer SSN Field and Vendor SSN Field according to where the kennitala is stored. The default is field 1, the card number. If you store the kennitala in another field, select it before processing data.
- Set Customer has Social Security Number with hyphen according to whether the kennitala on new cards should contain a hyphen. This also applies to vendors created from the list.
- Enable Insert additional Customer info when creating new customer/vendor if information should be filled in when a card number is validated. See creating a card.
- Select Data source and complete the connection according to your choice below.

Web service
Select Web Service and fill in Ferli XML Web Service and Ferli Password with the values supplied by Ferli. Get Data from Company Registry selects company lookup for company identification numbers when the web service is used.

File
Select File and complete these fields:
| Field | What to enter and why |
|---|---|
| Azure Function URL; Azure Function Auth. Code | The URL and access code from whoever sets up the integration. The code authorizes execution. |
| Ferli IP/DNS; Ferli Port | The server address and port supplied by Ferli for file retrieval. |
| Base Filename; Update Filename | The correct file names at Ferli; the base file rebuilds the list, while the update file adds changes. |
| Ferli sFTP Username; Ferli sFTP Password | The company's access to files at Ferli. |
| Function Test Mode | Leave disabled when retrieving actual Ferli data. |

Data retention
Do not store any data processes a file temporarily and updates cards without retaining the imported register rows. Enabling this setting does not automatically clear older rows. To fill in new cards in this mode, also configure the web-service URL and Ferli password.
Save Fetched Files is a separate setting that retains file copies for troubleshooting, even when register-row storage is disabled. Enable it only if your company's retention policy permits this.
Use Fetched Files to open saved copies. Choose Download for the selected file or Delete Selected to remove selected copies from the system. If prompted to enable saving when opening the list, answering yes changes the retention setting; it does not retrieve older files again.
Verify it works
Create one card or fetch an update file according to your connection. Verify the name and address on the correct card. A saved password or authentication code is shown as text indicating that the value exists; this alone does not verify connectivity. Clearing a password or code field deletes its saved value.