The Writer Guide documentation says I can use my own custom document property
instead of a variable in a condition statement.
“Using document properties to hold metadata and information that changes” on
page 363 described how to set up a custom document property. You can use
that document property as the variable in your condition statement, or you
can create another document property field specifically for conditions.
----- (Chapter 14 "Working with Fields" of Writer Guide, page 377 in PDF)
When I type the name of the property, in a "Conditional text" function in
the Insert Fields Other dialog, I always get the first phrase, never the
second. So it seems my conditional test is being ignored or incorrectly
always returning True.
After seeing "DocInformation:" displayed when I choose View > Field Names, I
tried prepending that to my property name in my Conditional text function,
But that did not help. I always see the first phrase of the conditional
I get success when using a variable.
Is there some trick to accessing a Document Property in a function?
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
For unsubscribe instructions e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
- [libreoffice-users] Custom document property in a condition statement. How? · basil.bourque
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy