General

Re: FilterOwssvr

dsnightthunder — Tue, 03 Aug 2010 15:46:39 GMT

No - when we go to activate the form. My Sharepoint Admin is looking into it. Upon further testing, we found it was happening with everything - even stuff that had no Qdabra functionality at all.

Thanks again for all your help!! Once you get things working - Qdabra is awesome!!!

Re: FilterOwssvr

Hilary Stoupa — Tue, 03 Aug 2010 15:33:34 GMT

Hi -- I was able to publish this as an admin approved template without any issue. When are you getting this error? When you upload the template from the published location in _admin/UploadFormTemplate.aspx?

Re: FilterOwssvr

dsnightthunder — Tue, 03 Aug 2010 14:17:52 GMT

Here is the file. By the way, I really appreciate all your help.

Re: FilterOwssvr

Hilary Stoupa — Tue, 03 Aug 2010 13:08:34 GMT

Can you attach your template? Under the Options tab, you can attach a file. As I said earlier, we use this method in browser forms with no issue, so it must be something in your form or in IPFS. I can take a look, see what happens when I try to publish it.

Re: FilterOwssvr

dsnightthunder — Tue, 03 Aug 2010 12:59:33 GMT

Well - I got through all of that finally... There are no errors or comments in design checker. The form works perfectly in preview.

Now when I publish through the admin approve process I get an error that there is an invalid number field.

I am still just trying to test and get it working so I have only two dropdowns on the form and no number fields or variables that I applied. Would that be something in the code? Have you ever heard of this error?

Re: FilterOwssvr

Hilary Stoupa — Thu, 29 Jul 2010 15:16:09 GMT

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.

Re: FilterOwssvr

dsnightthunder — Thu, 29 Jul 2010 13:08:32 GMT

Thanks! I finally got it working in preview, but when I publish I get an error that says the form will only open in infopath because it has features not compatible with the browser?

All this thing has on it are the two dropdowns! What could that be?

Re: FilterOwssvr

Hilary Stoupa — Wed, 28 Jul 2010 21:36:37 GMT

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 editor.

Thanks for your feedback on the documentation, by the way. I'll take a look at it and file a case for review.

Re: FilterOwssvr

dsnightthunder — Wed, 28 Jul 2010 14:09:29 GMT

I put the command back onto a button and got it working...

How can I make it work without the button?

Re: FilterOwssvr

dsnightthunder — Wed, 28 Jul 2010 13:17:36 GMT

Yes. I am using QRules. Everything worked great when I followed the instructions - so I am pretty sure it is working. It filtered perfectly on the static command in the example.

The instructions for dynamically creating the command and applying it to the cascading dropdown scenario are very vague in my opinion.

I added the error node - no error. I really don't know how to do the Generate Guid thing. Are there instructions somewhere for that?

Re: FilterOwssvr

Hilary Stoupa — Tue, 27 Jul 2010 21:31:24 GMT

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 installed and working correctly in your form.

FilterOwssvr

dsnightthunder — Tue, 27 Jul 2010 21:05:52 GMT

I want to set up a cascading dropdown using FilterOwssvr. I am unclear as to how I pass the value selected in the first dropdown to use as a filter in the second dropdown.

In the second dropdown field I am using the rule: concat("FilterOwssvr /dsname=GetEquipDesc /filter=LinkTitle /value =", EquipType) Where the filter column in the list is LinkTitle and EquipType is the name of the first dropdown field. I also tried attaching this to a button, but it didn't work, either.

I am not a programmer, just a form designer... Can someone tell me what I am doing wrong? I would greatly appreciate it!