Hi there,

There should not be any incompatibilities between 2.24 and 2.25 program rules. 
Can you provide a login privately so I can debug and try to uncover the problem?

In program rules, NULL is not supported. You can use 
d2:hasValue('variableName'), this statement will be true if the value is not 
blank or non-existing. You can alternatively use #{variableName} != '' (double 
hyphens).

Best regards,
Markus

> 19. nov. 2016 kl. 06.43 skrev Immaculate Ayebazibwe <ekass...@gmail.com>:
> 
> Hi guys,
> We created Program Rules in 2.24 but after an upgrade to 2.25 they are not 
> working. Have you experienced any thing like this, or did we do something 
> wrong.
> 
> Also I have noticed that the system does not recognise NULL, Null, when I 
> inspect element it shows warning NULL is not defined.
> I tried using null, but this does not work as it should, in other wards i get 
> the opposite of the expected results.
> Any ideas? 
> Have there been any changes in the database?
> Because we have used NULL/Null/null both in program rules and indicators a 
> lot.
> I get the same results on Demo
> 
> Appreciate your response!!
> 
> 
> 
> Thank you and Kind Regards
> Immarcqulate. A (Emma Kassy) 
> 
> "You miss 100% of the shots you don't take."

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to     : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Reply via email to