# Known issues and limitations
# Incorrect date values
The synchronization code assumes that all date values entered without an explicit time zone are in the UTC time zone.
If there are sources that provide values in the local time zone (or a different one), this can lead to incorrect conversions and therefore incorrect values in other systems.
# No unique names in the ELO repository
Currently, all synchronized folders and documents must have unique names in the ELO repository for synchronization.
This restriction exists as most systems that can be synchronized require unique names, whereas this is not the case with ELO.
Currently, only one of the elements with an identical name is synchronized with another system. All other elements are ignored. The element that is synchronized cannot be predicted.
Information
Automatic renaming is planned for a future version.
The exact method for renaming is currently being analyzed.
# Special characters in the short name
SharePoint Online and OneDrive have restrictions with regard to the characters that can be used in file and folder names. This restriction does not apply in the ELO repository.
To enable the synchronization of files and folders with these special characters, the short name is checked for problematic characters and these are then encoded with percent-encoding (opens new window).
The following characters are always encoded: /, \, :, *, ?, ", <, >, |
The encoding of these characters is implemented by the system provider, and not the general synchronization system, as only the system provider is familiar with the character restrictions.
# Leading/trailing spaces in the short name
Normally, the ELOix removes leading and trailing spaces in the short name.
As ELO Sync synchronizes with other systems that permit leading and trailing spaces in the file and folder names, all leading or trailing spaces from external systems are encoded with the Unicode character U+2420/␠ (symbol for space) and are not removed from the short name.
For more information, refer to the FAQ entry Unusual characters in short name.
# Conflicts with unchanged Office documents in SharePoint
After changing the metadata of an Office document in SharePoint Online, the new data is automatically written in the file contents of the associated document.
This results in a new file version that must then be synchronized with ELO.
If a new working version is uploaded to ELO at the same time (for example, by a different user), a conflict is recognized that must be resolved manually.
The metadata within the Office document in SharePoint Online in particular is invisible, and therefore it may appear as if the document has not been changed at all.
# References in ELO
References are currently ignored in ELO, as there are unresolved problems in handling changes to associated elements.
# Conflicts with automatic mapping
If new elements are found during synchronization and these can be mapped automatically to existing elements, multiple conflicts may result for these elements if their data does not match.
This is a security measure, as ELO Sync does not know the original version and therefore cannot predict what data should be kept and what should be discarded.
Information
Different methods enabling automatic handling of these conflicts are currently in the pipeline. One example: by using the more recent data set.
# No duplicate check during filing
If new documents are found that should be filed to ELO, these are always filed as individual documents.
There is no duplicate check and therefore no references are created.
This is in part due to the fact that there are currently unresolved issues with references in ELO and how they are handled in ELO Sync.