Book a Demo

Author Topic: RTF Reports vs. user properties and fields  (Read 2525 times)

Happy

  • EA User
  • **
  • Posts: 55
  • Karma: +0/-0
    • View Profile
RTF Reports vs. user properties and fields
« on: February 10, 2010, 07:02:36 pm »
Hi,

This article was originally posted on the 'Automation Interface, Add-Ins and Tools' Board. Maybe its better posted here.
(Link: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1265708378)


Now to my question:

Is it possible to use standard RTF features such as user properties or fields properly?

I actually use build 850.

I detected that importing a RTF template which has user properties (those are displayed as fields in footnote or title page, i.e. version number, stock no.), results in generated documents or exported templates which have the user property section within the RTF deleted and fields changed to MERGEFIELD fields to which the original user property values are attached statically with the original value. (Update is greyed out).

The same happens when using even more standard document properties (i.e. filename).

My user property question:
Will there be a support for user properties in future or is there a workaround available? (Project constants could do this, but create some effort if there are more templates)

My standard field/doc property question:
I found a document on the EA site "Working with the RTF Generator", Dermot O'Brian, Sparx Systems 2009. There a button Overwrite Document Field is mentioned which may do at least the Job, that  at least the filename field of the template is dynamic even after report generation. (Thus, the Name of the generated Document can be changed before generation and after generation the field is still accurate).
In build 850 this button doensn't seem to exist, the open office button which is there instead doesn't seem to do the trick I would need.
Am I missing something?

Even some more specific documentation would be great!

Thanks in advance
Jake