Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Im getting this error when my document is less than 4 gb and it has only 500 rows.
Im trying to modify a excel file with a value in a particular cell
this is the value that i want in the cell
this is the excel wich has 500 rows
this is the configuration of the the service
Discussion posts and replies are publicly visible
I have a similar problem where the attachment file is only 70kb but it gives this error. Do we have a solution for it yet? Thank you
i changed my document cause it had too much repeated information and i wasn´t able to see the tomcat-stdout log in myappian portal cause i don't have access to it. if you have access to it you could see aditional information there about this problem and post it here to see if someone give us more info about this. cause i'm pretty sure i will get this error again sooner than later again.
I found this and I now have some more insights into how I can fix this error: KB-1708 Errors related to file size thrown when using the Export to Excel/CSV smart service - Appian Knowledge Base - Support - Appian CommunityIt's true that my download has a lot of repetitive cell values. I'm trying to fix it, hoping this will work out.
FIXED!
I simply removed the older file (70kb, 15 rows) and uploaded a new base file (with only headers, size: 10kb) and referenced to new file. Since the new file is all blank with only headers, repetitions shouldn't happen again. I believe that the older file caused error since the table I was querying has a lot of test data and tons of repetitions (say my name as Process Owner). Seems like this wouldn't usually occur in production/real data.