When a link relationship is created, there are two options for the Link Type:
Use Join Condition: One or more pairs of attributes are used to link the repositories.
Manually choose record(s): Deprecated. Do not use this. If you choose this option, link tables may not load.
If Manually choose record(s) is selected, a variety of errors can occur, including:
Linked Tables may not load or expand.
In a Repository View, if the Hierarchy button is clicked, the Hierarchy/Taxonomy Manager will appear, but it may get stuck in the loading state and fail to list the existing hierarchies and taxonomy.
Users may be unable to create the linked preference.
In the log:
<drive>:\Enterworks\logs\EnableServer\enable_webMaster_<service-id>.log
the below error may appear, or the error may appear as a server error:
EPIMLogger.severe - getRepositoryLinkRelationshipList EXCEPTION: user=<user-name> userId=<user-id> link=<name-of-link> linkId=<link-id> repoId=<repository-id> org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.enterworks.epim.shared.model.BlinkRelationship.blinkJoinConditions, could not initialize proxy - no Session
Other issues.
To fix this situation, the link must be deleted and recreated to use a join condition.