You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having some issues getting displayParagraphIf() to work inside of a repeated part of my document.
Overall the repetition of elements works, aswell as expressions being replaced with a list elements values.
However when trying to add comments to only display paragraphs inside the repeated part based on the elements value, the library seems to try to evalute the comments expression against the root object, not the current lists object.
Am I doing something wrong or is this simply not a feature and if so, is there a workaround for this?
While inside the template I'd then use repeatDocPart(children) and displayParagraphIf(value != null) inside the repeating part.
I'll then get an error saying it can't find the property "value" on type ObjectA.
The text was updated successfully, but these errors were encountered:
It’s still a bug and was requested a couple of times. We had the same issue and couldn’t solve it.
Comments also disappear in repeating parts as they get deleted after the first time they get resolved.
I'm having some issues getting displayParagraphIf() to work inside of a repeated part of my document.
Overall the repetition of elements works, aswell as expressions being replaced with a list elements values.
However when trying to add comments to only display paragraphs inside the repeated part based on the elements value, the library seems to try to evalute the comments expression against the root object, not the current lists object.
Am I doing something wrong or is this simply not a feature and if so, is there a workaround for this?
Demonstration Code:
While inside the template I'd then use repeatDocPart(children) and displayParagraphIf(value != null) inside the repeating part.
I'll then get an error saying it can't find the property "value" on type ObjectA.
The text was updated successfully, but these errors were encountered: