Skip to main content
J
jeremyp358383
May 16, 2025
Question

Export to excel not working in read-only grid, works in record list

  • May 16, 2025
  • 5 replies
  • 1 view

I created an interface via an array of components, i.e. 

{

rule!header_component,

a!gridField(

 ...

)

rule!footer_component

}

The grid is using a recordType for it's data, I enabled the export to excel button to the grid but when I click the button I get the error in the csv file: " Expression evaluation error: could not find variable 'model!parseModel' ". I have no idea what this variable is or where it could be from or what it does. I checked within the record list view, and that exports perfectly fine, it just doesn't work in the grid Interface I have.

5 replies

davidj137213
davidj137213
May 17, 2025

Check tomcat-stdout.log file and share if you find any errors in it, please

mathieud0001
mathieud0001
May 17, 2025

Odd. We can look at the logs but this sounds like a bug if the export works from your Record List View.

I would log a support ticket.

F
frankc499301
May 17, 2025

It seems the issue arises because your grid is using a read-only interface without the necessary context for model!parseModel, which is typically available in the record list view. You may need to manually configure the export context or check if the interface setup complies with Appian's export requirements. I ran into a similar structured output issue while working on data formatting for a PhD thesis writing service, and ensuring proper context resolved it. Hope this helps!

V
vijayp6380
May 19, 2025

create a site for your interface with the interface which has that read only grid.

You will able to export excel from the site but not from the interface

A
anilkumark2036
May 28, 2025

While trying to export from readOnly grid interface, we see this error in the file: " Expression evaluation error: could not find variable 'model!parseModel' 

If you save this interface and cofig to a site and try, you will get the data in the file. From the interface object, parsing cannot be done.

Terms & ConditionsAccessibility statement