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! I'm working on version 24.3 with Spanish as the primary language, and I've added a document upload component (a!fileUploadField) to an interface with validation to receive only an XLSX document. I used a file originally with an .xlsx extension and it validates well, but if I manually change the extension to .pdf so it converts, for example, and then upload it, I get an error that I didn't capture in my validation: "File could not be uploaded. Reason: The file extension does not match its underlying file type." It doesn't actually upload the document, and the error persists even without the attached document. Or if I upload another correct document, I have to refresh the entire page for it to stop appearing. Is there a way to bypass this validation and just leave the one I have manually, or is there a way to update the validation when a new document is uploaded?In this part of code, local!excel is not a refresh variable, is just: localVariables( local!excel, ...)
Discussion posts and replies are publicly visible
This message appears because the PDF file type is blocked in the Admin Console under 'File Upload' using file extension blocking settings. The error will remain visible until the user manually refreshes or interacts with the interface; it does not clear automatically. One solution is to allow the file type at the admin level and then apply your own field-level validation in the interface(Make sure to create generic file upload to have consistency)
Hi! Thanks for your quick response, but I don't think that's the entire problem. If I upload a file that was originally a .pdf, it doesn't show this error, only my validation message. The problem lies in manually changing the file extension. If it was originally an .xlsx and I changed it to .pdf, it seems to become "corrupted" and the metadata doesn't match. It may have something to do with the administration, but I don't have access to it. However, .pdf files are accepted because they are attached elsewhere in the application. Thanks again.
How you are changing file extension?
From my local desktop, what I do is create a new Excel file, which creates an empty document with an .xlsx extension (for example: test.xlsx):
Changing a file extension manually does not alter the actual file content, so Appian blocks uploads when the extension and content don’t match. You cannot upload such files in Appian.
Yes, that's correct, Appian shouldn't allow it. What happens is that the error message doesn't go away even when uploading a correct file. This disables the form and forces the user to refresh the entire page and start over. It's fine that the message may appear, but it shouldn't persist when uploading another correct file.
Once you upload the correct file, the message should disappear. Make sure you are uploading the document to the same variable that is used in both the value and saveInto parameters.
There's a longstanding and known bug where, for instance, if a user tries to upload a document that's actually empty (which Appian disallows), that then even after they clear that upload and try uploading a valid file, the error message still (incorrectly) persists. It sounds like, if what Eleeeeeeeeena is saying here is true, a similar (incorrect) behavior might be persisting on the "document type mismatch" error, which I haven't confirmed (or tested) for myself, but would not surprise me whatsoever.