Export SQL to Excel plug in

Certified Associate Developer

Good morning,

I'm trying to obtain a report from a grid. I obtain that grid via an SQL query so I thought of using the SQL to Excel Smart Service included in a plug in for Appian Community Edition, but i haven't been able to obtain the desired result due to "java.lang.reflect.UndeclaredThrowableException". My configuration is the following (I filled the fields marked with * as I guess they are the only required ones and also a couple of the not required ones):

-Add as a new sheet=true

-Jndi Name= (I copied and pasted the connection url I'm using in the connected system)

-sheet_name="output"

-sheet number=0

-sql= "EXEC dbo.spRepRevenues '', ''" (which I know works due to the grid showing in the interface using .results)

-document name to create (not required): "probandoplugin" 

-document save directory (not required): "PM Artifacts"

My only guesses are that either the jndi name is wrong (I also tried using the name of the connected system object without success) or some of the not required fields need data. The other fields of that node are:

 Cell keys, cell values, document to overwrite, excel base template, include header row, sheet number to clone and starting cell

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    I think that the JNDI name should be the name of the datasource as used in the datastore. The default data source is "jdbc/Appian".

    I am not sure whether the plugin supports executing a stored procedure.

  • 0
    Certified Associate Developer
    in reply to Stefan Helzle

    Hi Stefan,

    for the JNDI name I used the connection URL used in the connected system object because I saw it began with "jbdc:sqlserver://", and watching the "jbdc/" or "java/jbdc/" pattern being used in other topics about the plugin (which were made years ago, hence this topic was created) I thought that would be the right one to use.

    About the stored procedure part, the only thing I can say is that I created a stored procedure to send the query as a parameter and it worked right (I tested it in an expression rule), but I guess I may also try a simple query

Reply
  • 0
    Certified Associate Developer
    in reply to Stefan Helzle

    Hi Stefan,

    for the JNDI name I used the connection URL used in the connected system object because I saw it began with "jbdc:sqlserver://", and watching the "jbdc/" or "java/jbdc/" pattern being used in other topics about the plugin (which were made years ago, hence this topic was created) I thought that would be the right one to use.

    About the stored procedure part, the only thing I can say is that I created a stored procedure to send the query as a parameter and it worked right (I tested it in an expression rule), but I guess I may also try a simple query

Children