The “No Label” error on Arkevia blocks the display or ranking of documents in the digital vault, without a clear explanatory message. It most often manifests as an empty label instead of the category name or document type, making navigation and sorting impossible. Understanding the mechanisms that trigger this anomaly allows for action before it spreads to the entire document space.
No Label Error on Arkevia Related to Bulk Imports: The Most Common Scenario
The majority of occurrences of the “No Label” error appear after a bulk import of documents or a data migration from a third-party system (ERP, payroll software, HR tool). During these transfers, the metadata associated with each file – document type, category, label – may not match the fields expected by Arkevia.
Read also : How to Create a Green Space on Your Roof?
When a file arrives without valid category metadata, the platform assigns it an empty label. The document does exist in the vault, but it becomes invisible in search filters or displays with the mention “No Label”.
For those looking to quickly resolve the no label error on Arkevia, the first step is to check the source file used for the import. A simple column shift in a CSV file or an empty cell in the “document type” field is enough to generate the anomaly across hundreds of rows.
See also : How to calculate the fiscal horsepower of your vehicle?
Pre-Validation of Import Files: Checklist Before Injection
Waiting for the error to appear before reacting forces you to correct documents one by one in the interface. A pre-import validation procedure eliminates nearly all cases.
- Check that each line of the import file contains a non-empty value in the field dedicated to the label or category of the document. Cells containing only spaces are treated as empty by Arkevia.
- Compare the labels used in the source file with the exact list of categories accepted by the target Arkevia space. A difference in case, a missing accent, or a special character causes a silent rejection of the label.
- Test the import on a limited batch (about ten documents) before launching the full transfer. This control pass allows you to detect mapping inconsistencies without contaminating the entire vault.
- Keep a timestamped copy of the import file. In case of a problem, this record allows you to precisely identify which lines generated orphan labels.
Diagnosis of Synchronization Conflicts with Third-Party Tools
The “No Label” error does not always stem from a manual import. Automated integrations between Arkevia and other systems (payroll software, accounting solutions, HR platforms) can also trigger it. The mechanism differs: here, it is the regular synchronization that injects documents with incomplete or outdated metadata.
Field Mapping Between Systems
Each third-party tool uses its own nomenclature to describe a document type. A payslip may be labeled “fiche_paie” on the payroll software side and “bulletin_salaire” on the Arkevia side. If the connector does not correctly translate this field, the document arrives without a label recognized by the platform.
The correction involves reviewing the mapping table configured in the connector. This table links the categories of the source system with those of Arkevia.
| Source System | Original Label | Expected Arkevia Label | Result if Not Mapped |
|---|---|---|---|
| Payroll Software | fiche_paie | Payslip | No Label |
| Accounting ERP | note_frais_2024 | Expense Note | No Label |
| HR Tool | contrat_CDI | Employment Contract | No Label |
| Manual CSV Import | (empty cell) | – | No Label |
This table illustrates the most common cases. A single mis-mapped field is enough to generate dozens of documents without a label in each synchronization cycle.
Updating Connectors After Arkevia Evolution
Platform updates may change the list of accepted categories or their format. A connector configured several months ago continues to send old labels that no longer match the current categories. After each Arkevia update, the mapping must be re-verified.
Preventive Maintenance: Purging Orphan Labels on Arkevia
Even with clean imports, orphan labels can accumulate over time. An orphan label is a category that existed in the Arkevia repository but has been deleted or renamed, leaving the associated documents without a valid attachment.
The cleaning process is divided into two phases. The first involves identifying the affected documents by filtering for the absence of a category in the management interface. The second involves reassigning them an existing label, either manually for small volumes or through a corrected re-import for larger volumes.
Scheduling this cleaning once a quarter reduces the risk of accumulation. Companies managing several hundred documents per month in Arkevia find that orphan labels regularly reappear if no maintenance routine is established.
Persistent No Label Error: Paths When Standard Corrections Fail
In some cases, the error persists despite complete metadata and verified mapping. Two technical causes deserve examination.
The first concerns the browser or application cache. The Arkevia interface may display outdated data if the cache has not been cleared after a correction. A complete page reload (Ctrl+Shift+R) or a log out-log in often suffices to refresh the display.
The second concerns a server-side issue, where the reindexing of documents has not been triggered after a bulk modification. This operation depends on the administrator of the Arkevia space or the platform’s technical support. The end user cannot initiate it alone.
When neither of these paths works, the support request should include the import file used, the identifiers of the affected documents, and a screenshot of the error. These elements speed up the diagnosis on the publisher’s side and avoid back-and-forth communication.