Why putting a field (i.e., {pega:reference.name}) in the header of a word document does not work?
We are using word template to generate a word document using some fields from the word object in both header and footer and also the body.
Where the body renders the fields properly. The header and footer still shows the field codes and not the field values.
Has anyone encountered this issue/situation before. Or does anyone has a solution or recommendation for this. Please advise.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
GB
Pegasystems Inc.
FR
Hello,
Which Microsoft Word version do you have ? If I do remember correctly, we were trying to avoid that kind of references in header and footer because on some situation it could be breaking the word page numbering. I don't think you will be easily able to do it on your PRPC 6.1sp2 but I will need to verify.
Accenture Australia Pty Limited
AU
Hello Marc,
Thanks for your reply. We are using MS Office 2010.
On doing some analysis myself I understand that its an issue with Word, as Word doesn't allow form fields (or any form controls) to be placed in headers, footers, footnotes, endnotes, and a few other places.
However, if there is a workaround by which we can achieve this that would be really helpful.
Thanks!!
Accepted Solution
Pegasystems Inc.
GB
Hi,
As far as I am aware, the use of PRPC Field Codes within Word header / footer areas is not currently a supported feature of PRPC. The code that interprets the PRPC specific Field Codes and inserts the corresponding property or Corr instance does not operate in the header / footer areas. I would suggest the following options that could be investigated further by you if the requirement for header / footer use is absolute and cannot be mitigated.
Option 1: Very Basic
Sizing the page of the Word document with no/minimal header and footer and placing the required text in the absolution position at the end of the page. This assumes / requires little dynamic text inclusion in the template and is probably not a viable and manageable solution.
Option 2: More Involved
Take a look at the Support Article ""Word merge: Fields in headers and footers not merged"" at https://collaborate.pega.com/discussion/commit-cannot-be-performed-because-deferred-save-instance for an approach to use features in Word to add header / footer entries.
Accenture Australia Pty Limited
AU
Hi Gareth,
Thanks for your reply.
As I understand, its a two way problem(both PRPC and Word) as I understand (by going through some blogs/discussions on internet on using word field forms by some other developers in their applications) that its an issue with Word, as Word doesn't allow form fields (or any form controls) to be placed in headers, footers, footnotes, endnotes, and a few other places.
Also thank you for sharing your thoughts/workarounds options. It seems option 2 is a more appropriate one, will give it a try .
Many thanks!!
Bank of America
US
Hi ,
Is this still an issue with v7.3?
Thank you
Tarun
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
Hi,
As far as I am aware, the use of PRPC Field Codes within Word header / footer areas is not currently a supported feature of PRPC. The code that interprets the PRPC specific Field Codes and inserts the corresponding property or Corr instance does not operate in the header / footer areas. I would suggest the following options that could be investigated further by you if the requirement for header / footer use is absolute and cannot be mitigated.
Option 1: Very Basic
Sizing the page of the Word document with no/minimal header and footer and placing the required text in the absolution position at the end of the page. This assumes / requires little dynamic text inclusion in the template and is probably not a viable and manageable solution.
Option 2: More Involved
Take a look at the Support Article ""Word merge: Fields in headers and footers not merged"" at https://collaborate.pega.com/discussion/commit-cannot-be-performed-because-deferred-save-instance for an approach to use features in Word to add header / footer entries.