-
I think you're on the right path. I'm assuming field_country is the node in the main data source. If so, try using current() instead. This means InfoPath will use the current value of the node you're on (that is, the dropdown) as the filter in your rule.
Let us know if this works!
-
What did you think of my advice above?
-
If you have a Submit button, you could disable it (or Hide it) if count(.) <3. Would that be enough?
-
You could use separate fields for the three input fields, and then concatenate those into the "back end" value.
I'm attaching a sample form. You can save it down, open it in design mode, and take a look at what I've configured. Then preview the form to try it out.
Hope this helps!
-
Hi-
The schema and the canvas (views) are separate. What does this mean? It means that you can design your schema, and your schema has a field called my:textbox.
Then you design your view (or views) and you can include the same schema node as desired. For instance, you can drag the schema node into each view. Or you can display the schema node ...
-
The obvious thing is a line break between the two sections - I assume you've checked that.
The other thing to check is the section's margins. It might be that there's a large margin somewhere creating the extra space.
Also check the section and table rows height. It should be auto - it might be set to a fixed number.
Hope this helps!
-
Hi Santosh-
Rule B should execute even if Rule A fails, unless
(a) Rule B depends on whatever the result is from Rule A
(b) There's a condition on Rule B
(c) you've checked "Do not remaining rules".
Can you check whether your rules are in one of these three scenarios?
Thanks!
-
Sorry if I misunderstood.
My understanding was that you have an InfoPath 2010 browser form that submits via qRules 4.2. If it's a browser form then it must be published to SharePoint and if it has qRules, then it's either using the sandbox or it's admin deployed.
Do you have a SharePoint mapping in the SharePoint tab?
-
Hi-
Could I suggest a workaround? Modify permissions so that everyone (NT AUTHORITY\Authenticated Users) is allowed to Add.
This is necessary because, when using sandbox, users authenticate as the service account, so the service account needs permissions to add.
Let us know whether this helps. Thanks.
-
If you mean a promoted property in your form (and thus a column in a form library), you should have the options First, Merge, etc when promoting the field. If you're only seeing the first entry, perhaps First is selected. Try to modify your promoted properties and use Merge instead.