dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #47687
FW: Bug in XML export / import for Program Rules
-
To:
DHIS2 Developers <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
-
From:
Sam Johnson <samuel.johnson@xxxxxxxxxx>
-
Date:
Thu, 10 Nov 2016 23:15:09 +0000
-
Accept-language:
en-GB, en-US
-
Authentication-results:
spf=none (sender IP is ) smtp.mailfrom=samuel.johnson@xxxxxxxxxx;
-
In-reply-to:
<28BE7E4D-948A-4CB5-B2A2-137E6F313811@qebo.co.uk>
-
Spamdiagnosticmetadata:
NSPM
-
Spamdiagnosticoutput:
1:99
-
Thread-index:
AQHSO1JAo/1oCB4s0UW5IkBJ6O/ab6DS2eqA
-
Thread-topic:
Bug in XML export / import for Program Rules
Hi all,
Using 2.25, revision 221c5d8 (Wed morning), Chrome
I just wanted to report a bug in the XML export / import for Program Rules:
· When you export XML for a program rule, ‘&&’ operators are kept as plain-text in the XML that is exported.
· When you re-import this XML, it crashes with the following log:
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '&' (code 38) (expected a name start character)
If converted to character codes (‘& &’) they import fine, so I’m guessing the export routine just needs to be updated to convert them on export.
This is a blocker because the ‘and’ variant doesn’t seem to work for Program Rules (they fail to fire), so you are tied to using ‘&&’ in expressions.
Cheers, Sam.
Follow ups
