-
Running a qRules command always involves setting a value to the Command field in the Qdabra Rules data source. Please have a look through the Quick Start Guide. That should fill you in on the basic idea of using qRules.
-
I don't know of any strict limit. 16 is the maximum number of times that a field can cause its own value to change, either directly or indirectly, and that can't be changed. But generally you shouldn't use recursive logic in your form anyway.
-
Could you show us some screenshots of how your conditions are set up?
-
There's no way to conditionally control which views appear in the view menu, but if you disable the view menu and use buttons to switch between views, you can of course hide those buttons conditionally. Ideally, this is the preferable way to control switching between views anyway.
-
You're going to need to give us a bit more detail than that. What does "hide a view" mean?
-
Hello tberch,
Adding custom code is enough to break qRules. When this happens, the following steps should be enough:
Click the remove code button
Save and close the form
Re-inject qRules
Have you tried carrying out all of those actions, in that order?
-
Hello shniggens,
Would it be able to just insert the new row at the beginning of the whole repeating group, and use a filtered SetValue command to set the requisite category field appropriately? That way it would definitely appear at the top.
-
Hello sentinelace,
It appears that you haven't defined any rules in the SquareRoot data source at all. You need to imitate all of the rules that I have on the Start and Step fields.
Also, I mentioned that I uploaded a simpler implementation than I had before. It looks like you still have the old one. Please download the ...
-
Hello Geronimo,
Before installing Query Builder, could you ensure that you don't have any InfoPath windows open, and if that still doesn't work, could you check Task Manager and kill any INFOPATH.EXE processes that might be running?
Just to double check, you do have InfoPath installed on the machine where you are installing Query ...
-
How about having two fields for the date difference? One (RawDateDifference) holds the result of qRules DateDiff calculation, and the other (AdjustedDateDifference) holds the value that takes the time into account? Then when RawDateDifference or the time change, just recalculate AdjustedDateDifference.