Excel Tools

IIRC most of the Excel Tools functions use a zero based index for the Sheet Number attribute. Try using a 0 for that input

Thank you Tim, I had come to that conclusion myself as well. I have tried a number of variations. Increasingly it seems that there is a bigger problem in our environment (or with the Excel Tools) as we can't get a number of them to run....

Do you have a full stack trace you can share? When parsing Excel to a CDT I've previously had a lot a problems with datatypes on the Excel side matching to Appian, in the end I think I would often have a CDT that was all TEXT attributes and then cast it natively within Appian to the correct set of types.

I'm attaching it here.

 

AdminServer.log

And here's the debug log

Hi Richard ,

For smart service input, cdt:={'type!{urn:com:telus:types:SCE_Case}SCE_Case_IncidentCategory'()}
I would suggest to pass the process variable directly of type SCE_Case_IncidentCategory list. And also The cdt field names should match the column header names in excel file.

In output we can map the same process variable.

Not sure if you grabbed the right time slot for the app server log, since I do not see any exceptions in the stack trace pertaining to this plugin.
One thing that was recently reported is that blank rows in the Excel can cause the smart service to fail.

It was in there, but perhaps buried too deep, here are the relevant lines:

####<Apr 24, 2018 4:09:21,212 PM GMT> <Notice> <Stdout> <btln007664> <AdminServer> <Appian Work Item - 1011 - ProcessExec01 : UnattendedJavaActivityRequest> <<WLS Kernel>> <> <8b0f9be8-c68f-4104-af6d-332817149a02-00000446> <1524586161212> <[severity-value: 32] [rid: 0:51:775] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <2018-04-24 16:09:21,212 [Appian Work Item - 1011 - ProcessExec01 : UnattendedJavaActivityRequest] ERROR com.appiancorp.process.engine.UnattendedJavaActivityRequest - An error occurred while executing activity: id=268439593, classname=com.appiancorp.ps.exceltools.smartservice.ParseExcelFileToCDT
java.lang.NullPointerException
at com.appiancorp.ps.exceltools.smartservice.ParseExcelFileToCDT.run(Unknown Source)
at com.appiancorp.process.runtime.framework.DefaultActivityExecutor$1.lambda$call$0(DefaultActivityExecutor.java:119)
at com.appiancorp.plugins.PluginUsageLogger.runWithPluginInformation(PluginUsageLogger.java:52)
at com.appiancorp.process.runtime.framework.DefaultActivityExecutor$1.call(DefaultActivityExecutor.java:119)
at com.appiancorp.process.runtime.framework.DefaultActivityExecutor$1.call(DefaultActivityExecutor.java:112)
at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:25)
at com.appiancorp.process.runtime.framework.DefaultActivityExecutor.execute(DefaultActivityExecutor.java:112)
at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:83)
at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute0(UnattendedJavaActivityRequest.java:55)
at com.appiancorp.process.engine.ContinuationRequest.executeOuter(ContinuationRequest.java:71)
at com.appiancorp.process.engine.ContinuationRequest.execute(ContinuationRequest.java:84)
at com.appiancorp.mdb.UnattendedRequestHandlerBean.onMessage(UnattendedRequestHandlerBean.java:37)
at com.appiancorp.mdb.UnattendedRequestHandlerBean_kegq7u_MDOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.MessageDrivenLocalObject.invoke(MessageDrivenLocalObject.java:127)
at com.appiancorp.mdb.UnattendedRequestHandlerBean_kegq7u_MDOImpl.onMessage(Unknown Source)
at com.appiancorp.ra.workpoller.WorkItem.run(WorkItem.java:59)
at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:72)
at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:47)
at weblogic.connector.work.WorkRequest.run(WorkRequest.java:123)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)>

I have also tried this approach. By this time, I have tried every iteration of variables in the Data->Inputs field. I suspect we have a larger issue at hand here.

R

If anyone can confirm that they've used this plugin successfully on 18.1, that would be great!