Export to Excel error: Exception in async action null

0
Hi, We are encountering some issues in some exports to Excel, using the standard Export to Excel buttons. The datagrid does contain all the data and works properly. However when pressing the export to excel button we get the following errors: java.lang.IllegalArgumentException: This data table 'Organisation_Person.Entity' doesn't have the column 'Organisation_Person.Organisation_DebtorInformation_Current'. at aV.a(SourceFile:177) at aS.getColumnIndex(SourceFile:50) at gp.a(SourceFile:117) at gp.a(SourceFile:119) at gp.a(SourceFile:70) at go.a(SourceFile:306) at go.a(SourceFile:255) at go.a(SourceFile:123) at go.a(SourceFile:81) at go$a.a(SourceFile:436) at go$a.execute(SourceFile:414) at hD.execute(SourceFile:27) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:457) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) and An error has occurred while handling the request. [User 'XXXXX' with roles 'XXXX, XXXX, XXX'] java.util.concurrent.ExecutionException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{}', all database changes executed by this action were rolled back at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at gz.a(SourceFile:95) at gz.execute(SourceFile:69) at jd.a(SourceFile:319) at com.mendix.externalinterface.connector.RequestDispatching$Worker.a(SourceFile:170) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.a(SourceFile:161) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.apply(SourceFile:160) at akka.actor.Actor$class.apply(Actor.scala:545) at com.mendix.externalinterface.connector.RequestDispatching$Worker.apply(SourceFile:156) at akka.actor.LocalActorRef.invoke(ActorRef.scala:910) at akka.dispatch.MessageInvocation.invoke(MessageHandling.scala:25) at akka.dispatch.ExecutableMailbox$class.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:223) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:123) at akka.dispatch.ExecutableMailbox$class.run(ExecutorBasedEventDrivenDispatcher.scala:195) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.run(ExecutorBasedEventDrivenDispatcher.scala:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) at akka.dispatch.MonitorableThread.run(ThreadPoolBuilder.scala:192) Caused by: com.mendix.core.CoreRuntimeException: Exception occurred in action '{}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.c(SourceFile:515) Caused by: java.lang.IllegalArgumentException: This data table 'Organisation_Person.Entity' doesn't have the column 'Organisation_Person.Organisation_DebtorInformation_Current'. at aV.a(SourceFile:177) at aS.getColumnIndex(SourceFile:50) at gp.a(SourceFile:117) at gp.a(SourceFile:119) at gp.a(SourceFile:70) at go.a(SourceFile:306) at go.a(SourceFile:255) at go.a(SourceFile:123) at go.a(SourceFile:81) at go$a.a(SourceFile:436) at go$a.execute(SourceFile:414) at hD.execute(SourceFile:27) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:457) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) In fact the message states: OrganisationPerson.Entity' doesn't have the column 'OrganisationPerson.OrganisationDebtorInformationCurrent This is correct, the entity does not have a column with this name, it is a relationship/association. things seem to be mixed up. Kind regards, Brian Update: Figured out that the issue is caused by the use of generalisations. Our entity named Entity is used as generalisation for entity Organisation and for entity Person. The mentioned debtor current column (actually an association) is an association between the Debtor entity and the Organisation entity. The error is caused by records that contain a relationship with a Person entity (which does not have a relationship with the Debtor entity). The datagrid does display the data as required and does not encounter any issues with this construction. My assumption is that the Excel export should contain the exact same content as the datagrid and follow the same validations/logic. I will log this as a support call.
asked
4 answers
0

Check the 'reference' tab, there have been incorrect references in previous versions.

answered
0

I would file a bugreport for this. Excel export should just always work. Out of curiousity I would try to do a csv export to see if that does work.

Regards,

Ronald

answered
0

Filed a bugreport. Nominated for release in future mendix version.

answered
0

Have the same bug in my application (Mendix 4.8.2). This situation will occur when:

  • your datagrid has a column to an attribute of another object

  • AND this 'lookup' via the attribute path returned an empty value

Is the solution planned for release?

answered