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.

Reload documents after content model change

stevegreenbaum

I’ve seen discussions of how some content model changes can create the need to unload and then reload the documents in order for the xml model change to properly take effect. I have a situation with a large database (50M+ documents) that has 300 base document types. Those 300 will be organized within numerous parent types. I expect some will be three levels deep.

My question is if I move a subtype from under one parent to live under a different parent type (by changing the xml type definition), will that cause me to have to reload any documents in order for the new hierarchy to be in effect?

Find more posts tagged with

Comments

mitpatoliya

Yes, I think you will require that
as all the properties from parents are inherited to the child
As you are going to change the parent it will change those set of properties.
In case you are not reloading the documents it will be inconsistent in the old and new documents.

stevegreenbaum

Thank you for your response.

Having to reload is a concern for me, especially since there are a large number of documents and that number will be growing over time. Certainly, changing a document hierarchy is not a common occurrence once a system is stable, but still a concern.