-
Did you use the design checker to see what the errors are? We currently have browser forms published to our test sites using qRules and FilterOwssvr, and they can be opened in the browser.
EDIT: I should also mention that since qRules injects code, you'll need to admin approve your template. This is covered in the user guide.
-
Hi -- I know with forms that use a database as their main data source, you can add additional fields to the data source -- but only to the root node. Perhaps this is also true of forms with a Web Service as a main data source? If not, you could create an XML file and add that as a secondary data source, bind your optional sections to a group in ...
-
That is an interesting result you are getting! I've attached another copy of your template -- I added a rule on the repeating group bound to the multi select list box that does effectively the same thing as your default value -- I think with both of them in place (kind of a belt and suspenders approach) the template does what you are wanting...
-
Wow. That is some kind of ugly, isn't it? Is this in client or browser?
-
Look under Tools / Form Options and find the Open Rules, if that is what you are talking about. If you are, instead, talking about the Submit rules, you'll want to look in the Submit Options.
-
Well, that depends what you are doing -- I added the command in a field rule, so I could use a field value in my filter. My command looks like this:concat("FilterOwssvr /dsname=owssvr /filter=LinkTitle /value=", .)
With that last underlined dot having been selected by clicking "Insert field or group" in the formula ...
-
Are you using qRules? FilterOwssvr is a qRules command...
Can you add the Error node from your QdabraRules data source onto your form, and check to see if you get any information returned there when you run the command? Also, try a simple command like GenerateGuid, and verify a Guid is returned to the results node, so you can ensure qRules is ...
-
Hi -- thanks for updating, and sorry I missed your original post.
So you know for next time, if you create a new thread, we are more likely to see it. Also, did you notice the "Errors" node in the QdabraRules data source? That can help with trouble shooting -- it will return any errors.
-
Hi -- sorry if this is a silly question, but why not just have one ClientCode field and put it in a repeating group?
So you know, there isn't a way to copy / paste in the data source, but you can use a reference to have two fields with the same name....
-
I added a new field for the Submitter's user name in the main data source. I added a rule that runs on form open to populate that with the username, if it is blank. I modified the submt connection to submit via rules. I added rules and a couple more email submits to show you what I mean. Hope this helps.