-
Yes, you probably would want to change your sort to sort by date modified. Then you can use conditional formatting to hide all but the first three rows. The formatting condition goes on the repeating row or section, and will be something like this (right click the repeating SharePointListItem data node in the fields task pane and select ...
-
You can arrange the data fields however you like on the form - is that what you mean? Or do you mean you need the rows sorted differently when you load the data? You can attach a screenshot under the Options tab in a reply (or a sample form) if that makes your question easier to explain. :)
-
For the condition on the option table (rule 3) - you only need a single condition. Change the first dropdown in the condition dialog to "The expression" and paste in:../../my:Main_Repeating_Offer/my:Main_Repeating_Comment[my:Main_Comment = current()/my:Option_Comment]This means:Navigate up to the Main_Repeating_Offer group ...
-
You have rules on the date of birth field that are displaying those dialogs. Just remove the rules....
-
You may have already gotten this, but wouldn't it be:
([a-zA-Z0-9_\-\.]+)@xyz.com(\s*,\s*([a-zA-Z0-9_\-\.]+)@xyz.com)*
-
Oh - sorry, I hadn't thought to mention that! Glad you have it working. :)
-
Here's another copy. I also added a translate function to your "age" default to get rid of the NaN error when DOB is blank.
-
Oh - I've seen this before. Sometimes IP doesn't include a field by default when the user adds a section. Under the properties for the repeating section, you can edit the defaults & you'll see something like this screenshot. I'll add another reply here w/ your form fixed up, but wanted you to know about this setting.
-
Here's a fixed up copy. Save the linked file locally, right click the saved file & select Design to open in design mode. I moved your field into the repeating group in the form's schema (also did that for your file attachment control that looked like you wanted it repeating). I see you have given some fields names - be sure before you ...
-
Oh, I usually add a status field for something like this. Save button sets status to Saved, submit button sets status to Submitted. Workflow to send email then has a condition that checks that status is equal to submitted prior to sending the email. Make sense?