Skip to main content
G
gauravs0010
May 20, 2021
Solved

Export SQL to EXCEL

  • May 20, 2021
  • 10 replies
  • 1 view

Hi Experts,

Earlier we were using Export SQL to Excel for generating the Excel from the db having 387 columns.

This particular service has got deprecated, how can we get this undepreciated or if there is any other workaround to generate the same.

Tried using Export Data Store Entity to Excel but it not working beyond 50 columns, when trying to break the colomn into set of 50 and then trying to right in next 50 column the previous column data is getting deleted.

Best answer by mikes0011

Not that this is a "supported" answer or anything, but last I checked, Export SQL to Excel still works just fine despite being deprecated.

10 replies

davel001150
davel001150
May 20, 2021

Do you mean 387 rows?  Or do you honestly mean that each row contains 387 named data elements?

G
gauravs0010Author
May 20, 2021

Its 387 columns David, rows are more than 50K.

Export data store entity to Excel have limitation of 50columns hence can't use that smart service.

csteward
csteward
May 20, 2021

Also to confirm, is this a one-time data load, or are you building a process to import this massive excel file regularly?

mikes0011
mikes0011Answer
Brainy
May 21, 2021

Not that this is a "supported" answer or anything, but last I checked, Export SQL to Excel still works just fine despite being deprecated.

Mike Schmitt, First Annual Live-Build Challenge Loser™️
    G
    gauravs0010Author
    May 28, 2021

    Hi Mike,

    Thanks for your response, I tried to use the same, its working fine but when I'am trying to make use of some base template which have some colored coded cells  and formula its giving below error..

    Export SQL to Excel was working fine till version 2.0.0 of Excel tools, currently we are on version 2.2.0 of Excel tools and  Appian 20.4...could it be a possible reason..?

    [mention:bf674657f8da4aa1b3b1cc5d28f94bb2:e9ed411860ed4f2ba0265705b8793d05]

    mikes0011
    mikes0011
    Brainy
    May 28, 2021

    I'm really not sure, I assume that depends on the template you're trying to feed in.  I don't know if any behavior was altered in the versions of excel tools which would affect this.  For your template I'd double-check that it's freely editable by a user opening it in Excel, etc, but after that I'm not sure what to suggest.  Maybe making a new copy of the template could help.

    Mike Schmitt, First Annual Live-Build Challenge Loser™️
    davel001150
    davel001150
    May 28, 2021

    I honestly think that the real problem, much as you might not want to admit it, is that you have a database table with 387 columns.

    I really wish there was a way to write 387 in all caps.  387!  That's beyond incomprehensible.  That should be about 7 or 8 tables.  The reason export to excel is limited to 50 columns is because you really should be limited to 50 columns too.  I think Appian might be justified in upping the cap to 100, for those cases where one table has to go 65 or even 78, but no one should ever actually reach the cap of 100 columns in a single table.

    You are going to face problems of all kinds from all sides, and your project is going to be painful to update or maintain, possibly quite painful to use, unless you refactor that.

      Terms & ConditionsAccessibility statement