InfoPath Dev

Hi,

Good day. I just want to inquire if Qrules do have a command to build dynamic URL that can be use to change REST URL to filter a SharePoint List.

An example would be as below.

I have 3 Dropdown as below. The value of the dropdowns needs to be use as a filter value in changing the REST URL connection to the SharePoint List. This would work fine if all the 3 dropdown all have values, I can build the URL as concat(http://servername/_vti_bin/ListData.svc/ListName?$filter=Product eq", "'",ProductValue,"'", "and Category eq", "'",CategoryValue,"'", "and Brand eq", "'",BrandValue,"'", "")

 

Product: Gadget

Category:

Brand: mybrand

 

Is there a command in Qrules to make the above work if one of the dropdown is blank?

 

Regards,

Rommel 

 No, I don't think so - I think you just need separate rules for setting the URL based on the possible combinations - or you could probably use a complex substring formula (like the one outlined here - http://blogs.msdn.com/b/infopath/archive/2006/11/27/conditional-default-values.aspx).

I'd probably add a secondary XML form logic data source for this and just use rules - see the attached file.

Hi Hilary,

 The form that you had sent is what exactly I needed for the logic. I'm not so familiar regarding the secondary XML data source so I may need to check how it works. Do you have a blog or a link for example where I can read through to learn how to use the similar XML source that you had use on the form.

 

Thank you once again for the help.

 

Regards,

Rommel 

Well - you can export that exact same XML under the Resource files in the Data tab in the ribbon for the form. You can then import it into your form, and add a data connection to it. From there, you simply need to implement the same rules. :)

Hi Hilary,

Good day. I did try to use the form that you had sent but when I use the "REST Url with Filter" from the XML data source as the value to change the REST URL and requery the data connection, I'm getting the below error.

 XML data that is required for this form to function correctly cannot be found.

 

Am I doing something wrong. Kindly advise.

 

Regards,

Rommel 

Can I see your form? You can attach it under Options in a reply.

Hi Hilary,

Good day. I had attached my form now. But the connection to the dropdown are all connection to a sharepoint list. Please let me know if I need to provide anything else.

 

Regards,

Rommel 

 I took a quick look at your logic and it appears ok - what is the URL you are getting in the REST Url With Filter field?

Hi Hilary,

Attached is the result if I put some filter value. 

Also, the form has another view called PM. I'm using the same process in filtering on it that when the dropdown change, I'm building the below REST URL as below and this is working fine

 

concat("https://home.smecnet.com/sites/itcdev/debtors/_vti_bin/ListData.svc/WIPWorkbench?$filter=ProjectManager eq ", "'", ., "'", "")

 

 

Sorry, I'm confused - in the screenshot above, when you click the button in that view, you get the error "XML data that is required for this form to function correctly cannot be found"?

Yes Hilary, the error happens when I click the button.

It looks like a valid REST URL, to me at least. I'm assuming you also get an error if you paste this URL into your browser's address bar?

Yes an error also happens. but on the form that I had sent you and on the PM view (page), when I build the REST URL using the below process, it is working fine. not sure why it is not working on the MGT View.

 

concat("https://home.smecnet.com/sites/itcdev/debtors/_vti_bin/ListData.svc/WIPWorkbench?$filter=ProjectManager eq ", "'", ., "'", "")

 

Hi Hilary,

Sorry about this, I had figure out and it is my mistake. The issue is on the list name, it should be "WIPWorkbench" and what is in my secondary XML data connection is "WipWorkbench", and from this I learn that it is case sensitive.

 

Thank you once again for having a look into this and sorry as it is my mistake in configuration.. 

Nothing to apologize for - good eye to catch that, and great to know about it being case sensitive.