The development group I am on is currently only able to use version 15.2.20152.1027 and I need to capture the file name on error. I am able to capture filename on size limit errors but not on an invalid file type. The documentation here: https://www.igniteui.com/help/api/2019.2/ui.igupload#events:onError (which does not have a version stated) states there is a fileId available, this value is not present on the same level as errorCode or errorMessage as the documentation suggests. Is the fileId available with my version? Are there other options to get file information onError?
Thank you for posting in our community.
You can retrieve the file name in the fileExtensionsValidating event handler. After this event, if the file is invalid, the control cancels the upload and does not collect any information about the file.
After reviewing my initial inquiry it was not detailed enough.
I am getting the file name in fileExtensionsValidating event handler, this works great. Is there a way to get the file name o during the file size check? We are using the multi-file upload configuration with 1 simultaneous. With this configuration when a file exceeds the size restriction, it also is removed from the file list.
We have multiple upload instances on a page with different ids, each with its own filetype and filesize restrictions. I am attempting to gather the file name and specific uploader the error came from to output it in a table of failed uploads so users have a reference of which files failed where and why.
Any insight is greatly appreciated.
At this point we do not support retrieval of the file name during file size validation. What I can suggest in order to see this functionality implemented is logging a new product idea. You can suggest new product ideas for future versions (or vote for existing ones) at https://www.infragistics.com/community/ideas.
Submitting your idea will allow you to communicate directly with our product management team, track the progress of your idea at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Remember when submitting your idea to explain the context in which a feature would be used and why it is needed as well as anything that would prevent you from accomplishing this today. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it.