I am using a!fileUploadField component in UI. When uploading a file which is inside a folder (as below) the uploaded file name is changed by Appian to display as CDAOF-~1
File Path:
C:\Users\asrivastava\Desktop\TEMP\Level 1 Nested inside this folder name to get long name of folder\Level 2 Nested inside this folder name to get long name of folder\Level 3 Nested inside this folder name to get long name of folder/CDAOF- WM Alternatives- PC Confirmation.pdf
Please let me know if any resolution for this issue.
Discussion posts and replies are publicly visible
a!fileUploadField provides a keyword to customize file name fileNames, you can leave it blank to uses the original file name. Test by not setting fileNames and also check if the files are renamed in the process.
Can you share a code snippet of what you are suggesting.
Adding fileNames didn't seem to work.
a!fileUploadField(label:"Test",target:tofolder(1020980),value:ri!documents,saveInto:{ri!documents},maxSelections: 1,fileNames :fv!file.name)
Snippet:
a!localVariables( local!temp, { a!fileUploadField( label: "File Upload", labelPosition: "ABOVE", validations: fv!files.name & "." & fv!files.extension, saveInto: local!temp, value: local!temp ) } )
If the red text is different from the source file name then there maybe an in issue with your Appian instance. I suggest to go to Appian support.
Thanks for sharing the snippet. Again this has nothing to do with instance. As i said this is specific behaviour only observed when uploading file from a folder which is nested deep withing folders resulting in long folder name. If you can try the path i shared on your instance you would understand and have the same experience.
You're probably hitting a Windows OS-level filename size limit constraint, in which case it isn't really an issue within Appian, you're merely observing a side-effect of filename truncation that would be happening anyway.
That's likely a reason.
But It's strange to not see correct name of an uploaded document while it's visible correctly in the folder itself. And how would you explain that to users.