I am getting a stacktrace error when I generate a pdf document. It works with some but not with all. Is there a way to debug this error? How do I set local the Document Exporter lognode to debug mentioned in this post: error generating pdf Regards, Ronald An error has occurred while handling the request. [User '1657' with roles 'Medewerker, SA'] -------- com.mendix.core.CoreException: Exception occurred in action 'Microflow [MutatiesKoppeling.PrintMutatie]', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.d(SourceFile:553) Caused by: com.mendix.core.CoreException: Exception occurred in microflow 'MutatiesKoppeling.PrintMutatie' for activity 'Generate PDF (.pdf) document using template 'MutatieTemplate'', all database changes executed by this microflow were rolled back at kT.b(SourceFile:252) Caused by: java.lang.IllegalArgumentException: The given member name 'TypeInschaling' has no corresponding member in this object of type 'Basis.Arbeidsvoorwaarden' at aR.getValue(SourceFile:306) at aE.a(SourceFile:97) at aE.a(SourceFile:43) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at ak.a(SourceFile:33) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at ak.a(SourceFile:33) at ck.a(SourceFile:223) at aE.a(SourceFile:70) at ck.a(SourceFile:223) at ck.a(SourceFile:180) at bf.a(SourceFile:81) at c.a(SourceFile:89) at c.a(SourceFile:56) at dp.a(SourceFile:104) at kT.a(SourceFile:67) at eU.executeAction(SourceFile:96) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:49) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:473) at iw.b(SourceFile:155) at com.mendix.core.Core.execute(SourceFile:191) at dD.execute(SourceFile:183) at jx.a(SourceFile:299) at jx.a(SourceFile:230) at jx.processRequest(SourceFile:174) at fI.a(SourceFile:71) at com.mendix.core.MxRuntime.processRequest(SourceFile:938) at com.mendix.m2ee.server.handler.RuntimeHandler.handle(RuntimeHandler.java:42) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1007) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:747) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:209) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:662)
Found at last the problem. Part of the template was copied from another template. On the row there was a condition for visibility set. The problem was that the entity used could not be found because that entity belonged to another entity (not the one that holds the data).
In my opinion the modeller should generate an error when this entity can not be reached from the dataview in a template.
Caused by: java.lang.IllegalArgumentException:
The given member name 'TypeInschaling' has no corresponding member in
this object of type 'Basis.Arbeidsvoorwaarden'
Is Arbeidsvoorwaarden an enumeration field? Have you changed the values in this enumeration recently? It may be that you have an old value in your database which now no longer exists for this enumeration. The solution is to edit the database directly to remove these old values (or add the 0old values back to the enumeration, clean up the data in Mendix, then remove the old values)
Comment here because of the space...
Yes, it is a enumaration field. But as far as I can tell there have been no changes. We have the entity arbeidsvoorwaarden and a shadow entity arbeidsvoorwaarden temp. In the temp we have this entity and not in the other one. In the pdf I show the old value arbeidsvoorwaarden and the changed (temp) one. In the temp I show this entity. But the pdf crashes on the arbeidsvoorwaarden part (where this entity is not showing) and not on the part temp where this entity is shown.
Removing arbeidsvoorwaarden from the template solves the problem. But this part has nothing to do with TypeInschaling. That part is coming out fine in the next section.