We have the same issues in one Aurena page where we have done changes in Page Designer (PostingProposalHandling). Suspect framework changes that does not handle messaging in combination with local page changes.

For us to fix the issue we have unpublished the changes. We plan to add the same Page Designer changes from scratch to see if that works. If you have done local changes in your Aurena page you can try to do Unpublish to see if the N/A messages disappears. We also found that some general messages that were given in IEE client showed up with a valid message.

Hi, We had a meeting with a couple of IFS technicians who gave us the  same explanation as you did in your comment; Framework changes  and removal of contexts.

We had this error in several pages, and it will take some time to reconfig. 

I was not able to read this in any of the release notes,  presentations for UPD14 & UPS15, or in the analysis run pre- installation… 

If this is the standard for future Updates, we will struggle with local adjustments of Aurena.

Just to let you know another strange behaviour we have reported to IFS after Update 16: We have added an event that throws an error message if a user book less than one full hour at wage code for holidays. After update 16, the error message is thrown, but the Save button is not working even if the user correct the absence. This is an effect we have seen after Update 16 - leading us to think there are more unhandled stuff regards to message handling in Aurena. Also note that this is in an Aurena page NOT changed in Page Designer.

Latest updates from Statnett:

We have now started from scratch and added the Page Designer changes but unfortunately we still experience the error messages. In general there is incorrect message handling in Aurena; We get a lot of N/A messages and sometimes Illegal operation on perfectly valid changes.

The actual Page Designer change we have identified will lead to this error is when you re-arrange groups in a window. For instance the Posting Proposal window we have moved the Posting lines group before the Invoice Lines group. Doing so we get the incorrect error messages and cannot save the changes. If we just remove buttons or other minor changes, there are no errors in the window.

A step-by-step description is reported to IFS and hopefully they will respond quickly and give us a solution to this problem.

Hi,

We have also experienced the same after upd16, have you heard anything from IFS about any solution of the problem?

IFS claim they have fixed the issue in UPD19, and as this is a framework change they cannot supply a single patch. So until we install the next update we have made a workaround by changing the order of elements in posting proposal window (as listed above). Now only a few N/A messages rise - not for all users and not all the time - and we hope this is gone after installing update 19 sometimes later this year. In our experience the quality of IFS updates haven’t been excellent - we have found show stoppers both in Update 13 and Update 16. Hopefully the next update we go for (most probably Update 20) will be of better quality as these errors introduced after updates give us a lot of extra work and not so happy end users.