-
I'm just wondering - when you set the start date in your load rule, are you using yyyy-MM-dd format? Because I just tried to reproduce this and could not - I've attached a sample form, save it locally, right click, select design, from there you can take a look at the logic, preview, etc. My table has 3 rows included by default, and is set ...
-
You could use custom validation to at least mark the field invalid, I think. I found a suggested pattern here, and tested it here - it at least found your ™ and ®. Your field could have custom validation - if the data matches the custom pattern of [^\x00-\x7F], mark the field invalid and give the user a message about removing the ...
-
This sample shows a technique for only emailing a section in a view. Put your email address in the Email To field and click the Send button. The rules on the send button set a field that is used for conditional formatting of the sections of the form.
-
This can vary based on your AD setup. What I do is drag the data fields onto a form and then preview - that should show you all the available keys for your account...
-
Actually, we added it because people often find the double eval syntax confusing.
Looking at the formula you tried, my guess would be that this would work:
xdMath:Eval(xdMath:Eval(../../my:Enclosures_Messages/my:Attachments/my:Attachment/my:FileAttachment, 'concat(@my:qRulesFilename,";")'), "..")
With a relative path ...
-
Well - it takes custom code (or qRules) to add rows to a repeating table using code.
However, you could include a number of rows by default and based on the user's selection determine how many to display. Look under the Data tab in the ribbon and on the left you'll see a button for Defaults. You can insert multiple instances of a ...
-
Under the File tab in the ribbon, in the left hand column select Publish. In the middle column, select Network Location.... Unless maybe this is a SharePoint List form?
-
That's because I'm silly and forgot something.
string viewName = MainDataSource.CreateNavigator().SelectSingleNode("/my:myFields/my:GoToView", NamespaceManager).Value;
-
You'll need to get the value from the field - C# would be (with your XPath to your node replacing the bold text, of course):
string viewName = MainDataSource.CreateNavigator().SelectSingleNode("XPATH TO NODE GOES HERE", NamespaceManager);
Then you can use the variable in place of "PMI"
ViewInfos.SwitchView(viewName);
-
Okay - there isn't really a way to unpublish in terms of setting the template to no longer "know" it has been published without saving the form as source files and changing the manifest.xsf. However, if you publish it to a network location (like a spot on your hard drive, for example), it will no longer be able to Quick Publish to ...