I want to create "title" constant in my template that I can insert in multiple places. Fields doesn't seem to do this. Is this possible?

I want to create a constant with the document title that I can insert on the title page, the TOC, and as a page header. I tried using the “title” field, but I don’t see any way to set the value. Is there some way to create a named constant for a document and then insert it?

The Title field gets its value from document properties.

  • Select menu item File - Properties
  • Click the Description tab.
  • Title is the first field of the dialog.
1 Like

I don’ have File.Properties in Writer 7.3.1.3

File Properties

You can restore the defaults to your File menu by clicking Tools > Customise select the tab labelled Menus and in the field Target select File then click the Reset button to restore menu to default settings. Cheers, Al

1 Like

Looks like a platform unknown to me. Is that the host system or some guest install running on VMware?

I cannot find any reference to “simplified” or otherwise compacted menus for any context, and the picture does not look like one of the alternate user interfaces available to me (currently on v.7.2).

If @EarnestAl’s suggestion for menu reset does not solve your issue, state your system setup (Operating system, hardware/virtualizing platform, LO build) so someone with better knowledge can tell us what is going on here.

Workaround

Use a “user field”:

  • Menu item Insert - Field - More fields …
  • Tab Variables
  • Select User field in the left pane
  • In the text boxes below the selection panes, type a name for your field and a value to display.
  • Click Insert

You can now insert that field anywhere in your document. With this, you can right click any instance of the field to edit value, and it will update everywhere.

In some ways, user fields are easier to work with than the proper title field, but they do not appear in file properties, which may be desirable for achival/management purposes.

1 Like

Thank you! I shot myself in the foot…

Thanks for the solution tick but @keme1 actually answered the question. Best to mark his original answer as solution. I just provided an answer to the speed bump on the way to the solution. :slight_smile: