Skip to main content

I have two attachments on the form, but when I open the attachment control settings, I am unable to see the setting to set the attachment control as default (on either control.)

 

Currently using 'IE' mode in Microsoft Edge. Have also tried doing this in the defunct IE browser, but this does not make any difference. I am unable to publish the form because I get the message that the form "does not contain a default attachment control"

Hi,



 



Do you see the same issue with Chrome?



Does the site have a custom masterpage?



What version of Nintex Forms are you using?




  • Same experience with Chrome. Adding another attachment to the form prompts the "Does not contain a default attachment control" error, but when opening the settings for each attachment control (and I have been using the "Controls in Use" option on the ribbon to ensure that there are none hidden) there is no option to set it as the default control


  • The site does not have a custom masterpage as far as I am aware.


  • Forms version 87




 



Thankyou


Version 87 sound like the version number of the form and not the version of Nintex forms you have installed.



When you are in the Nintex Forms designer navigate to Help > About Nintex Forms and a panel will popup which has your forms version.



Something like this:




Yeah, sorry, my mistake.

Version: 2.12.1.30

Hi,

That build is over a year old and was a hotfix release at the time. Might be worth upgrading to the latest build to see if that resolves your issue. You can download the latest build from the Nintex customer portal.


Thankyou for bringing this to my attention. Not sure about the process for that. My pro Nintex colleague left the business after Nintex was installed. I'll see if it can be updated and then hopefully that will resolve it.


You could try another PC to make sure its not the PC that is the issue. Also trying another user account will eliminate if its your user account that is the issue.

Thankyou for your assistance. I believe you are right in identifying it as being probably caused by an older build.


Reply