-
You cannot validate a section.
You would need to check the value of each checkbox field.
This can be broken up with multiple fields.
-
what you can do is combine them as expressions with and/or and then consolidate multiple to one line.
I think there are some examples here.
-
Hi Jeetu.
A template is a vital peice of the solution. When a document is made from it, that document always retains a link to the template since the template is required for it to be rendered properly.
A template cannot be copied, it must be published so that InfoPath can provision itself properly.
You would need to send the XSN to someone who ...
-
You can do this without code.
Create a field in your form which will hold the email address that you will use for the email data connection.
Then just use a rule with your conditions which uses the set field action and the concatenate function to build the three addresses.
concat("who@you.com; him@them.com;", Email)
You can use ...
-
The only way to get around clients not having InfoPath installed locally is either to use Terminal Services or Citrix to host the application remotely or to use InfoPath Form Services so that a server can host the forms and render them in a browser for the users.
IPFS is expensive and requires the enterprise Sharepoint so you would have to find ...
-
I would think you would do the same as attachment process but just use an empty string. this should overwrite the field reference but have not tested.
-
It sounds like you have InfoPath 2007.
You will get different results depending on whether you are using Outlook or not since it interprets InfoPath attachments and HTML.
-
You need to go through the publishing process in designer and you would need both connectivity from your PC to the Sharepoint Site and adequate permissions to be able to publish the template to it.
-
Hey Dean.
Unless I have to I prefer to build my workflow logic in the form itself.
I think that is easier to setup and maintain than a SP workflow.
Yours might justify it but typically most workflows do not need that level of detail and it ends up just complicating the solution.
I am not sure if there are any issues with IP2003 and designer ...
-
First I would say that you should name the fields in your form schema better, something more descriptive. Then ideally it is the same name you want in SharePoint.
Even if you reference it you can do so by Display name, which appears has a typo and is Filed1 in what you pasted there.
You could try publishing again to a new library and ...