Ability to validate attachment controls
In Nintex Forms 2013 when creating validation rules, it would be useful to be able to validate the attachment control. The attachment control, when named, does not appear in the list of named controls. It only appears in Item Properties. I have tried various ways and could not get the validation to work (isNullOrEmpty using self on the attachment control, using the attachment item, property, etc)
Brian
shared this idea
Hi all,
With the development of Universal Forms, we are including accepted file types, rule-based logic for required/not-required, maximum number of files, minimum number of files, and maximum file size. This should also include invalida characters.
If you have any other requirements, please let us know in the comments section below.
Cheers,
Euan
24 comments
-
Allan Helbling
commented
In my opinion, I think this is mandatory to be able to use rules on attachments controls. For example : minimum 2 attachments if contract type is "Invoice", 1 otherwise
-
Hi Vas,
Yes the rules in Universal Forms can validate all types of controls. Its still a little while away from release, but I will update these suggestions when we get closer to release.
Cheers,
Euan -
vas
commented
Will this have rule based logic for validations of string or number as well?
-
Anonymous
commented
Well, this is a show stopper now for the new Applicant Tracking System I just wrote using Nintex Forms and Workflows.
-
Jimmy Hang
commented
Please don't forget to add File Name Validation option to the Attachment control, it will be best if the validation auto follows what's allow in SharePoint. Just experienced first hand what happens if the user attach a file with invalid file name to the form, and it's not nice.
-
Anonymous
commented
this needs to be done into the product
-
Ron
commented
I agree that this is a defect, not an enhancement. Users are not informed that they have attached a file with "invalid" characters in the file name and are not given a chance to correct the situation. Then the workflow fails and all functions included in that workflow are never executed.
-
ScottK
commented
I know it's a Nintex charter to try and get rid of JavaScript helps like this - please add the attachment validation soon...
-
Sven Adriaanse
commented
Please, validate unsupported characters within the filename on attachment in Nintex Forms. (& " : * ? <> # {} % ~ / \, I would also add comma "," and plus "+" to the list as non-recommended) and sequences like ".."
If there is an attachment added to the form in a Workflow task form the user receives an error and the tast never completes. Even worse: te workflow task is locked and the workflow is STUCK...
-
Tanuj
commented
May be this could help:
http://www.vadimtabakman.com/nintex-forms-attachment-required.aspx
-
Nathan
commented
Im encountering same problem too, hope someone helps. I am thinking about cutting file name due to attachment with very long file name is much worse when you have email notification with attachment. thanks for the help.
-
Ron
commented
I agree with Barry that this is a Nintex bug. The Nintex form should parse the attachment file name and report the error (invalid character) to the user immediately and require that it be corrected before submitting/exiting the form.
Currently it just waits for SharePoint to report the error after the form has been submitted, at which point it is to late for the user to fix (even if they understand what just happened).
I also agree with Eric - don't change the file name out from under the user. Better that they change the file name and re-attempt the attachment.
-
Anonymous
commented
any updates?
-
Andrew
commented
Adding the validations for minimum and max are helpful, but to have complete control on the dynamic validations, we will need NAMED CONTROLS added to the list of references.
-
Jeremy H
commented
We have several forms in our environment that generate user errors from the attempted attachment of file names with illegal characters. Would really like to see a built validation for these.
-
Andrew
commented
Any update on the Planned release? We still cannot use rules or use Named Controls within the reference. If we can use named controls then we can dynamically set the number of minimum by using a value in the named control
-
Stefanie Sloper
commented
Please add support to conditionally require an attachment.
-
Barry
commented
Nintex Forms breaks the standard SharePoint attachment name validation.
Within SharePoint standard forms characters such as ampersands are highlighted and users are prompted to correct any issues before submission. However, when using Nintex Forms there is no validation and any file name can be submitted by users.
This results in an exception when list items are created and renders Nintex forms useless for anything which relies on attachments.
-
Barry
commented
In my book the fact that using Nintex forms breaks standard Sharepoint functionality makes this a bug.
Not being able to confidently attach documents within a SharePoint form is ludicrous. At a minimum attaching a document should provide the same feedback that standard SharePoint forms offer.
-
Barry
commented
Validation of unsupported characters needs to be provided in Nintex Forms. It's a huge hole in attachment validation and leaves some serious gaps in attachment functionality.