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.

What mean 'residual' in node browser

ribz33

Hi,

i did my own type, i complete some properties with my own code.
When i look created node in node browser i see that some properties have residual=true and "property type" is empty because "value type" is fill instead.

Something is wrong or all is normal ?
What mean residual ?

Thx in advance.

Best regards.

Find more posts tagged with

Comments

jneeve

I noticed residual is true if I've applied a custom aspect to a document and then later on removed a property of that aspect.

Perhaps a way to try to keep integrity since removing properties from aspects when in use is tricky.

ribz33

Yup you had right…
Residual=true for all properties existing on node but not existing in model… (this can appear if you do a mistake in your QName in java code or if you change your model like you say)

In my view, its important to watch if there is residual property in node browser because this can be source of problems. For instance if you do a copy of a node, system will not copy this residual property (all value of residual property will be null).

Thanks for your help

jneeve

This post is a bit old, but does anyone actually have a proven method for removing a property for an existing custom aspect?

I suppose one way would be to make a new aspect with the changes, do a lucene search to find every document with the old aspect. Then loop through, add the new aspect and copy each property from the old one to the new one. Then, search again but this time remove the old aspect… Of course now all the documents have an aspect with a new name, so then you'd have to change every piece of code you've written to change the aspect name….

Personally, it doesnt seem to complain if you remove the property from the model - it simply marks it with a Residual=True. However I wonder about the long term implications…