Skip to main content
September 16, 2025
Solved

Issue Exporting Data with More Than 50 Columns Using "Export Data Store Entity to Excel" Plugin

  • September 16, 2025
  • 11 replies
  • 0 views

Hi Everyone

I'm currently facing an issue while exporting data from a specific table that contains more than 50 columns. I'm using the Export Data Store Entity to Excel plugin, but it throws an error during the export process.

Has anyone encountered a similar issue or found a workaround to export data with more than 50 columns successfully? Any suggestions or guidance would be greatly appreciated.

Thanks in advance!

Best answer by mikes0011

I believe it has a stated limit of 50 columns.

I believe the general suggested & supported solution, is to update the generated document with a 2nd pass through the smart service (starting at the 51st column, using the Starting Cell parameter) with any additional data.
EDIT: i take this back, data is truncated below the starting row even if a completely different set of columns is written to.  It's one of the reasons I find this node pretty much unusable.

My personal advice however would be to trim the columns you're exporting - do you truly need in excess of 50 columns?

I might suggest, instead, the JSON to Excel Plug-in.  Though I still think you should try to reduce your used columns to something lower than 50 if possible - 100 columns in a single excel is going to be too cumbersome for most user-facing use cases.

11 replies

mikes0011
mikes0011Answer
Brainy
September 16, 2025

I believe it has a stated limit of 50 columns.

I believe the general suggested & supported solution, is to update the generated document with a 2nd pass through the smart service (starting at the 51st column, using the Starting Cell parameter) with any additional data.
EDIT: i take this back, data is truncated below the starting row even if a completely different set of columns is written to.  It's one of the reasons I find this node pretty much unusable.

My personal advice however would be to trim the columns you're exporting - do you truly need in excess of 50 columns?

I might suggest, instead, the JSON to Excel Plug-in.  Though I still think you should try to reduce your used columns to something lower than 50 if possible - 100 columns in a single excel is going to be too cumbersome for most user-facing use cases.

harshk1671
September 16, 2025

As Mike suggested, there is a smart service limit of 50 columns.

I often encounter requirements where I need to export more than 50 columns. To handle this, I create multiple sheets, each containing a set of 50 columns.

Here I initialize first column of each sheet with the same unique identifier, which makes it easy to put VLOOKUP later to work in downloaded excel.

For example:

  • Columns 1–50 go into Sheet 1
  • Columns 51–100 go into Sheet 2
    ...and so on.

I pass the same document for update across all sheets.
Hope this helps!

September 16, 2025

Its Not Working going the above approach and old data erasing 

harshk1671
September 16, 2025

Are you using a new sheet when you re pass to smart service for next set of columns?
If you use the same sheet then it will overwrite the existing data.

Can you share your configurations of both the smart service nodes and process flow diagram?

shubhama926776
September 16, 2025

Smart service  has a known limitation of 50 columns.
I have explained my approach in earlier discussion.

https://community.appian.com/discussions/f/data/34813/how-to-export-data-to-excel-in-a-grid-with-more-than-50-columns

Try and let me know if that works for you.

June 18, 2026

Hi [mention:9861aef97eb2483a8b76175d9eda1e37:e9ed411860ed4f2ba0265705b8793d05] , In the above shared method when creating web api can I use the query entity template and it will be get method . Is that what you are doing there also we want to export all the rows availlable so I am not neccessarily going to pass any input in the body can we skip the parse or why we are using that I don't get it.

shubhama926776
June 18, 2026

Yes you can use a GET Web API and query the data directly. In my example, I parsed the request body only to read an identifier/filter. Since you want to export all rows and are not passing any input, you can skip the body parse and directly query everything, then pass the result to exportDataSubsetToBase64().