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.
Hi,
We have a code where a view data we are showing in a grid and user have to download the report but while downloading user is getting following error:
In the code we are using a user filter on a varchar field because of which there is data issue.
Interface Definition: Expression evaluation error [evaluation ID = 325b2:2a9f5] : An error occurred while executing a save: Expression evaluation error at function fn!createfilterfromrecord_appian_internal [line 24]: The passed parameter(s) are of the wrong type. Received the type com.appiancorp.common.xml.JaxbConversionException: error converting typed value TypedValue[it=1980,v={ASSESSMENT MI REPORTs,Assessment Report in MI Reporting,Qm7Kig,{81,,10d2b745-9e94-474d-928a-c623c6e7ca8a@_a-0000eccb-82f8-8000-9c64-011c48011c48_16707690,0},#"SYSTEM_SYSRULES_recordGridField
Discussion posts and replies are publicly visible
Check the saveInto code corresponding to the Download action. Looks like some parameter is being passed between objects and there is a data type mismatch between source and target. If you can share a code snippet will be better!
The error shows a complex object (with UUIDs/encoded references) being passed to a VARCHAR field filter. If you're using a user/group picker component to filter text data, Replace picker with a!textField or filter varchar on username strings directly.
Thanks for the reply,
Issue is fixed and error was due to data in one of the varchar field having bad character.