Open GoogleCodeExporter opened 9 years ago
At first please create your issue at
https://github.com/opensagres/xdocreport/issues
The split of mergefields is done by preprocessing. It seems that you have a
case which is not supported?
It should be very cool if you could create a test with your case like
https://github.com/opensagres/xdocreport/blob/master/integrationtests/fr.opensag
res.xdocreport.core.test/src/test/java/fr/opensagres/xdocreport/document/docx/pr
eprocessor/DocxPreprocessorWith2InstrText.java
Original comment by angelo.z...@gmail.com
on 9 Jun 2015 at 4:02
Hi Angelo,
Thank you for answer, I really appreciate your rapidness.
First of all, I've created this issue on GitHub.
https://github.com/opensagres/xdocreport/issues/37
Then, I'm attaching an example to this message, there ".. you can find a
template, scala/java code and resulting output. I need to implement my project
in scala so this template was processed using scala code too. But for your
convenience I've added equivalent java code"
I've been tried to find a bit more information what exactly is wrong and I've
found that as it's shown at screenshots every run has its own RSID parameter.
It serves for conveniet merging of documents and can be turned off. It could be
helpful, but..
- In the attached template "@before-cell#if($print.variableThree)" mergefield
was broken even without any RSIDs and wasn't filled correctly.
- In my project (sorry, I can't attach it) it seems that turnind RSIDs off
helped and fresh mergefields (I tested ones with "@before-cell" token - it is
the main headache) were really created as a single run. Whatever after
processing resulting table didn't contain some cells/rows/columns (I can't
guess a rule in which they are being deleted) as before.
Then I've tried to edit document.xml myself to make broken mergefields look
like ordinary ones. It didn't affect on template's view but my program began
throwing strange parse exceptions even if I've only removed really unnecessary
runs.
So I'm in panic a bit, please do something :(
Thank you!
P.S. I apologize for grammatical mistakes if you've found any
Original comment by NICKy103...@gmail.com
on 10 Jun 2015 at 10:41
Attachments:
Original issue reported on code.google.com by
NICKy103...@gmail.com
on 9 Jun 2015 at 3:35Attachments: