Help
Find the message you see or the symptom that applies. Check the connection and identification fields before repeating an import, because importing can change cards.
Connection and files
| Message | Explanation | What to do |
|---|
| Password is empty in National Register Setup | No Ferli web-service password is saved. | Choose Open National Register Setup and enter Ferli Password. See connection setup. |
| Error invoking web service | The request could not be sent to Ferli. | Check the web-service URL, network connectivity and whether the extension may send HTTP requests. Ask your administrator for help. |
| Error in response: … - … | Ferli returned an error code and explanation. | Read the explanation and check the kennitala and Ferli account. Contact your service provider if the issue persists. |
| Wrong data source selected. Please select "File" as data source to read the National Register Base file. | The action for fetching a base or update file requires file-based integration. | Select File in Data source and complete the connection settings. |
| Azure Function error (HTTP … …): … | File retrieval failed; the response provides further details. | Check the URL, authentication code, sFTP credentials and file names with your administrator. Do not share passwords or unreviewed response text. |
| Error getting the base file from the blob storage given by the azure function | The base-file download from storage could not start. | Ask your administrator or Rue de Net to check file retrieval before retrying. |
The web service can also display Ferli's own error text. In National Register Setup, open Web Service Logs for calls to the Ferli web service and their HTTP status. Azure Function errors appear in the error message or job queue run history; do not assume they appear in the same web-service log.
Cards
| Message | Explanation | What to do |
|---|
| Customer '…' does not exist. | No customer matched the kennitala in the configured identification field. | Check the field and kennitala. Create a card if it does not exist. |
| Vendor '…' does not exist. | No vendor matched the kennitala in the configured identification field. | Check the field and kennitala or create the card. |
| Customer: … is already registered. | No new card was created because a matching customer already exists. | Choose Open Customer Card and review the existing card. |
| Vendor: … is already registered. | A matching vendor already exists. | Choose Open Vendor Card instead of creating it again. |
Confirmations
| Message | Explanation | What to do |
|---|
| Are you sure you want to fetch the Base file? This will delete all entries from the current table and repopulate it. | A question before deleting and rebuilding the register list. | Answer yes only if you intend to rebuild the list. Use an update file for ordinary changes. |
| Are you sure you want to upload a base file? This will delete all entries from the current table and repopulate it. | Manual base-file upload deletes register rows and can update cards. | Verify that you selected the correct base file before answering yes. |
| Managed to get the base file. Do you want to read it into the table? | The base file is available for import; the previous register rows have already been deleted. | Answer yes if you intend to complete rebuilding. If you cancel, check the list before continuing. |
| Managed to get the base file. Do you want to update your customers and vendors with the data? | The base file has been read into stored register rows; you are asked whether to change cards too. | Answer yes to update matching cards now, or review the rows first. |
| Do you want to save a copy of the base file for troubleshooting? The update will proceed regardless of your choice. | Save Fetched Files is enabled and you are asked about a base-file copy. | Follow your company's retention policy. Answering no does not cancel the update. |
| The "Save Fetched Files" feature is currently disabled. Files from Ferli are not being saved. Do you want to enable the feature? | The fetched-files list offers to change the retention setting. | Answer yes only if the company wants to retain copies of future files. |
| Are you sure you want to delete the selected file entries? | Selected saved file copies will be removed. | Confirm only if they no longer need to be retained. Cards are not changed. |
Problems without a message
| Symptom | Explanation | What to do |
|---|
| The register list is empty after a run. | Do not store any data may be enabled. Cards may still have been updated. | Check Update Logs and the relevant cards; see retention. |
| Nothing updates although the card exists. | The kennitala may be in a different field from the one used by the integration, or the data may contain no change. | Check identification-field mapping, the kennitala and the latest file. |
| Name or address is not filled into a new card. | Additional information is disabled, the kennitala is unavailable when the number is validated, or data is missing. | Check the new-card route and connection. |
| Acceptance actions are missing. | The list was opened with Open National Register from the customer or vendor list. | Open RdN National Register List directly through search. |
| More cards change than expected. | The same kennitala can match both a customer and vendor. Accepting all covers all unprocessed rows. | Review both cards and use selected rows when you do not intend to process the entire set. |
| A card becomes blocked or remains blocked after an update. | Certain development codes block cards. Previous blocks are not removed automatically. | Review the development code and reason for blocking before an authorized employee changes the block. |
| The final count does not match the new cards. | The final count can include selected rows whose cards already existed. | Check the cards themselves and the messages saying they are already registered. |
| Two cards share a kennitala but only one changes. | The integration chooses the first matching card of each type. | Ask the person responsible for master data to review duplicates before running again. |