Export SQL to Excel" Smart Service issue after Appian upgrade to 25.3

Certified Associate Developer

Hi All,

I have a process which uses "Export SQL to Excel" Smart Service and fetches data from the db and creates a excel sheet.
When using this - generate report, we are creating a select query - SELECT ID AS Number AND LABLE AS 'Label Name' FROM ABC_TEST table (multiple tables with joins to create almost 172 columns), and the plug-in smart service uses these alias names and creates header into the template excel that is - in excel you can see 1st column ('Number') & 2nd column('Label Name') as But after Appian upgrade 25.3, this alias is stopped and it is now taking direct table column names that is - ID & LABEL in excel header.

Anyone has seen this issue and have any work around, please help/suggest.

Thanks in advance.

Note - this is user requirement where excel download report has almost 172 columns data which is used for further reporting. It was working very great before this upgrade but after upgrade it is just working with column header as like table header which is not desired.

  Discussion posts and replies are publicly visible

  • 0
    Certified Lead Developer

    As you already know, "Export SQL to Excel" is a plugin function, so generally this issue occurs with newer versions, and the plugin owner needs to update the plugin to provide support.
    I would recommend creating a database view with aliases and exporting from that view.

  • 0
    Certified Associate Developer
    in reply to Shubham Aware

    Thanks Shubham, we had already tried using view and again it's a query slowness and timeout issue were observed and again if we use view with alias to it, still the alias will not supported.

  • 0
    Certified Senior Developer

    Hello,

    I had a similar issue with that plugin (at least I think it's the same as there are multiple deprecated versions of this smart service, depending on what plugin you got)


    I didn't found a good definitive solution but I found that when using an UNION the alias is still used


    If in the end of all your selects and joins you add a dummy union, let's say

    (Your Selects ATM) UNION ALL (SELECT null as NUMBER, null as LABEL FROM ABC_TEST WHERE 0) for your example

    It keeps the alias in the excel header. The 'Where 0' is important so you don't add null values to your excel. Doesn't matter what you but before the AS LABEL, idea is jsut using the union to force the labels

    It's not an optimal solution but I hope this helps!