...
Need to handle orphan members and system relations during sync.
More control over which member to include, like Serie should be included with Arkiv but not with Arkivdel.
Control which field is searchable and/or searchable as a member. This should make the field limitations unnecessary. If not then need to make the field limitations configurable instead of hard-coding.
Include member’s/descendant's related system entities?
Although there are limitations on the number of nested members, they are not applied during syncing at the moment. Need to fix this.
Need to use Asta7 models and properties in Essync instead of duplicating them.
Multi-level nesting makes the search quite complex and might not be needed for all the projects. Should we consider adding support for flat nesting as well?
Multiple entities have fields with the same name and same type, but one of them has the CodeTableRef/FileName feature. The first field will be used.
Multiple child entities with the same name. The first one will be used. Note, that if there are more fields and/or child entities on the later entities those will be not available.
Should file content indexing be configurable?