-
A validation rule won't restrict the user but it will enforce validation, and the field will be labeled in red, warning them. All rules/validation only happen after the user tabs out of the field or uses the mouse to click away from the field.
A lot can be accomplished via code. I'm sorry, but I'm not the person to help with ...
-
The rich text box does not have the ability to enforce a character limit the same way a text box can.
You could try some validation such as string-length(.) > 100, then show a validation error.
As far as counting words, I've never seen this before. Maybe some code will be needed. Not sure though.
-
Hi-
Having a view to see the data and a view to insert data is fine. I don't think a separate form is needed.
But I'm a little confused by your question. A button should allow you to add an action to switch views. Have you tried this?
-
Hi-
You probably need a full xpath:
concat("Delete /xpath=my:myFields/my:Container/my:Orders/my:Order[", current(), "]/my:OrderDetails/my:OrderDetail)
Let us know if this works.
-
I don't think you want a default value. You probably want on load rules. On load:
1. Call now() and populate a field with the time (something like this might work: substring-after(now(),"T"). This rule does not have a condition.
2a. Condition: time > noon. Action: Set the field to today() + 5. You could use addDays.
2b. ...
-
Hi,
Isn't there a problem in the URL? I would expect something like:
http://<path to the XSN>?OpenIn=PreferClient&NoRedirect=true&XmlLocation=<path to XML>
Right now you are providing the same thing twice (the path to the ...
-
I don't think you could prevent them from choosing Station, answering that, then choosing Apparatus, then answering that, then choosing equipment and answering that.
One thing would be to provide instructions in the form, so they know to select one, answer and submit.
Another option might be to clear their previous answers if they switch ...
-
Membership xpath is only meant for document level permissions. What this means is an xpath in your form which stores the user alias of the person who will be granted access, for example:
my:myFields/my:manager
This field would store the manager alias and DBXL would be giving permissions to that user according to the document level ...
-
Your form can have various sections, and these sections can be shown/hidden (via conditional formatting) according to the selections the users have made in the previous questions.
-
InfoPath 2010 data connections to SharePoint lists include queryFields, which allow you to set up filtering before the data connection is executed. I'm not sure if this was covered in the master class. But anyway, once the queryField is set (that's your filter), you call the data connection, then you get the repeating data back in ...