Browser Forms

Re: Can you simplify an xPath to improve performance?

cpluce — Thu, 07 Jun 2012 12:47:26 GMT

I fixed it. It seems the owssvr connnection can only retrieve a limit amount of data records in a view. I need to research this. This is a problem. Maybe I can create a speical view just for this and set the item limit 9999.

This is why the filter value only works on some forms and not the others.

Is there anyway to remove the "22;#" or "any number;#" from in front of the assigned to field in a task list?

My form shows:

Approval: 22:#FirstName LastName

nevermind. I fixed this with the substring

Re: Can you simplify an xPath to improve performance?

cpluce — Thu, 07 Jun 2012 12:21:40 GMT

Thanks. I undertsand that I shouldnt retrieve data on form load. That was just an example of what I was trying to do. I have a rest connection that works and has the correct schema but I couldnt have sent that because it was for a client. I have a couple of data connections that work. The problem I have is trying to use the filter value with an ID that is stored in the current infopath library. It works with a drop down or textbox that is on the form like you explained in your example. The ID value I am trying to use for filter value is being retrieved on form load in another data connection that is from a sharepoint list. I probably didnt explain my self well.

I actually have it to query upon a view switch. Yes, the example data connection was to a list with no data. That schema was odd to me as well and wasnt sure that was different than my other form. I am going ot try somehting else today.

Re: Can you simplify an xPath to improve performance?

Hilary Stoupa — Wed, 06 Jun 2012 23:32:11 GMT

I added to this - save it locally, right click and select design. Looks like you weren't getting any data back in your data connections - your 2DS schemas look odd. You'll see by the notes I added in the form that I added a REST connection to an owssvr.dll URL - and I have actual fields in my schema. Does your list not currently have any data in it?

Re: Can you simplify an xPath to improve performance?

Hilary Stoupa — Wed, 06 Jun 2012 14:42:45 GMT

Sorry I haven't been able to get back to you on this yet - I'll try sometime today, but it may be tomorrow.

Re: Can you simplify an xPath to improve performance?

cpluce — Tue, 05 Jun 2012 16:35:01 GMT

I posted an example of what I am trying to do. Thanks

Re: Can you simplify an xPath to improve performance?

Hilary Stoupa — Mon, 04 Jun 2012 22:32:33 GMT

It is FilterValue1 - you'll want to be sure you have no typos. And what field are you selecting from your form that you are setting its value to? Are you selecting the field that would have the Task Id?

Re: Can you simplify an xPath to improve performance?

cpluce — Mon, 04 Jun 2012 22:32:03 GMT

can you give me an example of step 3. setting the field value? I think this is my problem.

Re: Can you simplify an xPath to improve performance?

cpluce — Mon, 04 Jun 2012 22:27:00 GMT

I got it. I just am not sure yet why I cannot get the FilterFieldValue1= to work the ID field.

Re: Can you simplify an xPath to improve performance?

Hilary Stoupa — Mon, 04 Jun 2012 22:23:56 GMT

I didn't concatenate it because it should not be changed - it should not be concatenated. If you look way back, you'll see you said that this works in a browser:

http://URL/_vti_bin/owssvr.dll?CS=65001&XMLDATA=1&RowLimit=0&List={5166419E-2DB1-4EA4-8911-FC12ADE6D57A}&View={13217A3C-60A8-4FA9-9662-7BBD1EB19FC8}&XMLDATA=TRUE&FilterField1=@ows_ID&FilterValue1=81

So, the only piece in the URL that you need to change using a concat formula is the very end to the right of the "=" sign - in the above URL, it is "81". @ows_ID is the name of the column. That text itself. Or, ID - FilterField1=ID. It is the name of the column you wish to filter on. It won't change. I really don't know how else to say this.

Re: Can you simplify an xPath to improve performance?

cpluce — Mon, 04 Jun 2012 22:14:03 GMT

I will try to simplify the form and send it to you. I just thought I could do it. I noticed you didnt concat the ows_ID.

Re: Can you simplify an xPath to improve performance?

cpluce — Mon, 04 Jun 2012 22:10:03 GMT

I changed it to this:

1. Change the REST URL
concat("https://portal.com/sites/_vti_bin/owssvr.dll?Cmd=Display&List=%7bA407888E-28F1-4EE0-98DD-82D7E6A65700%7d&View=%7b8190E33D-11DD-42E7-A1C6-9B84E2139979%7d&XMLDATA=TRUE&noredirect=true&FilterField1=", @ows_ID, "&FilterValue1=", field 7)

2. Query using REST

3. Set Field Value 99 to name task was assigned from REST connection

Re: Can you simplify an xPath to improve performance?

Hilary Stoupa — Mon, 04 Jun 2012 22:07:46 GMT

I provided a sample concat formula a few days ago:

concat("http://URL/_vti_bin/owssvr.dll?CS=65001&XMLDATA=1&RowLimit=0&List={5166419E-2DB1-4EA4-8911-FC12ADE6D57A}&View={13217A3C-60A8-4FA9-9662-7BBD1EB19FC8}&XMLDATA=TRUE&FilterField1=@ows_ID&FilterValue1=", Path to the field with your ID in it)

The part that says: Path to the field with your ID in it is where you'd select the field that has the value you want to filter on.

As I've mentioned before, if you want to attach your template to the Options tab in a reply, I'll take a look at it and see if I can help you, since I don't seem to be explaining this at all well.

Re: Can you simplify an xPath to improve performance?

cpluce — Mon, 04 Jun 2012 22:01:07 GMT

For step one - you are changing the field you are filtering on? I dont know. syntax typos.

Wouldn't that always be ows_ID? Yes

Wouldn't you want to change the value?

yes

So that the end of your url.

Is this concact?

&FilterField1=@ows_ID&FilterValue1= (select ID from data source)

FilterField is the name of the column you want to filter on, not some piece of data from your form. In your concat formula, you appear to be changing the FilterField to the value of some other field. I do not understand this at all.

FilterValue is what you'd want to set.Can you give me an example?

Step two is fine.

Step three, again, I don't understand at all. What field are you setting to the value of the URL in step three?

lets just say Field 99 with the value fomr step 1.

Why would you set the value of a field in your form to the URL value? Typo

Re: Can you simplify an xPath to improve performance?

Hilary Stoupa — Mon, 04 Jun 2012 21:51:40 GMT

cpluce:
1. Change the REST URL
concat("https://sharepoint.com/sites/_vti_bin/owssvr.dll?Cmd=Display&List=%7bA407888E-28F1-4EE0-98DD-82D7E6A65700%7d&View=%7b8190E33D-11DD-42E7-A1C6-9B84E2139979%7d&XMLDATA=TRUE&noredirect=true&FilterField1=", @ows_ID, "&FilterValue1=855")
2. Query using REST
3. Set Field Value to:
concat("https://sharepoint.com/sites/_vti_bin/owssvr.dll?Cmd=Display&List=%7bA407888E-28F1-4EE0-98DD-82D7E6A65700%7d&View=%7b8190E33D-11DD-42E7-A1C6-9B84E2139979%7d&XMLDATA=TRUE&noredirect=true&FilterField1=", @ows_ID, "&FilterValue1=855") (I really need to use the task ID field from the other data connection here)

For step one - you are changing the field you are filtering on? Why? Wouldn't that always be ows_ID? Wouldn't you want to change the value? So that the end of your url would be:

&FilterField1=@ows_ID&FilterValue1= (select ID from data source)

FilterValue is what you'd want to set.

Step two is fine.

Step three, again, I don't understand at all. What field are you setting to the value of the URL in step three? Why would you set the value of a field in your form to the URL value?

Re: Can you simplify an xPath to improve performance?

cpluce — Mon, 04 Jun 2012 21:36:10 GMT

OK I am going to try and keep it simple.

I have an Infopath library that is a workflow when an item is created. In this workflow I have task ID's that are created in this library. lets just say Task ID. This is stored in this infopath library/list. This ID is the exact ID in the workflow task list. This is sort of like a foriegn key to a primary key relationship. The data in this task list is what I am trying to recieve and display on the form so that the user does not need to click in the workflow link t osee when the task was approved or any comments.

I can get REST or Owssvr filter to work with filter values that I have in a drop down on the form. However, when try to use the task ID from the infopath list for the active form I get a blank.

I have 2 data recieve connections. 1 connection retrieves all ID's for the active form on form load. The 2nd data connection is a REST or Owssvr:(Neither one works) I think it is because it does not know what the filter value is yet because it is server side and I have to pass this in the URL first before I queiry the connection.

https://sharepoint.com/site/_vti_bin/owssvr.dll?Cmd=Display&List=%7bA407888E-28F1-4EE0-98DD-82D7E6A65700%7d&View=%7b8190E33D-11DD-42E7-A1C6-9B84E2139979%7d&XMLDATA=TRUE&noredirect=true

I am using the above with a filter applied on the field which works with the drop down list but not the ID field from the other data connection (ID's for all active forms)

I tried the 3 steps using as you mentioned aobve but it set's the field value to the URL itself and not the value.

1. Change the REST URL
concat("https://sharepoint.com/sites/_vti_bin/owssvr.dll?Cmd=Display&List=%7bA407888E-28F1-4EE0-98DD-82D7E6A65700%7d&View=%7b8190E33D-11DD-42E7-A1C6-9B84E2139979%7d&XMLDATA=TRUE&noredirect=true&FilterField1=", @ows_ID, "&FilterValue1=855")
2. Query using REST
3. Set Field Value to:
concat("https://sharepoint.com/sites/_vti_bin/owssvr.dll?Cmd=Display&List=%7bA407888E-28F1-4EE0-98DD-82D7E6A65700%7d&View=%7b8190E33D-11DD-42E7-A1C6-9B84E2139979%7d&XMLDATA=TRUE&noredirect=true&FilterField1=", @ows_ID, "&FilterValue1=855") (I really need to use the task ID field from the other data connection here)

Probably did step 3 wrong? Thanks for your help. I have been dealing with this for 2 weeks.