nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Assocation between content versions.

alexv

Hi,

I would like to create content association with the particular version of another content.
E.g.:

1) create items:
content v1.0
linkedContent v1.0

2) create assocation:
content v1.0 -> linkedContent v1.0

3) create new version of linked content:
linkedContent v1.1

actual result)
content v1.0 -> linkedContent v1.1

desired result)
content v1.0 -> linkedContent v1.0‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I tried to make association between nodes in version2Store, but I received "UnsupportedOperationException" as a result.

Is there any way to leave that association immutable? Or,
Is there any way to set the version of the linked content node explicitly, when association is created?

Thanks for any help or suggestions.

Find more posts tagged with

Comments

derek

Hi,
Manipulating the version store nodes directly is not something we support or have even considered as an option; but you're welcome to try if you wish.
The association is between the head versions of the nodes and not between the the source and the original version of the node; sorry, but the behaviour is really just a choice we had to make.
Regards