-
Ok, so let me try to get us on the same page here.
You've mentioned this list with 400+ items a few times. Is each view referencing the same 400+ item list, with the use of filters, or does each view make use of a different 400+ item list? If it's all the same list, are you re-querying it (i.e. re-triggering the data ...
-
You should use that file to create an XML File data connection, not a web service connection.
-
A NullReferenceException here will almost always mean that the node you are trying to select was not found. Is my:AllReq a field from before or from after the modifications?
We have tentatively looked into adding custom version upgrade feature to qRules, but unfortunately haven't come up with a good way to do it so far.
-
Is it the same query (set of data) for each view, just filtered differently in each one? If so, are you rerunning the query (i.e. do you use an "Execute Query" rule) every time you switch views?
-
Without taking business days into account, the following validation rule should work:Condition: date [Is less than] (Use a formula...) addDays(submissionDate, 10)To take business days into account, I think you'd need something like the DateDiff command in qRules (which has support for business days). Let me know if you'd like to give ...
-
How about adding a rule to the field like this:Condition: <field> does not begin with <prefix>
Action: Set <field> to concat('<prefix>', <field>)
-
It sounds like you just need to bind both tables to the same repeating group, and then display different information in the two of them accordingly. Would that work in your case?
-
You will need to set the dropdown to populate from a repeating group in either the main or a secondary source. Then you can use code to manipulate the XML items in that repeating group.
-
Unfortunately, to the best of my knowledge, InfoPath doesn't directly support keyboard events. What is it that you are looking to do?
-
That formula looks about as simple as it can get. What has led you to believe that this formula is causing the problem? I would think that the query is the more likely culprit.