Code

Re: REST query fails for end users

GMUDuckman — Fri, 01 Sep 2017 20:08:33 GMT

What error is is outputting? My guess is that Filer isn't passing along any authentication - can you setup the form up in a sharepoint infopath library and see if the form works properly if you open it in the browser?

Re: REST query fails for end users

Josee Sevigny — Thu, 24 Aug 2017 21:28:00 GMT

Sorry for the delay.

I've replaced the "personal" Code Signing certificate with a real one, still no luck.

Here's my code. Am I using it correctly?

cliLib = cliNo.Substring(0, 2) + "000";

//get the REST connection
FileQueryConnection fq = (FileQueryConnection)this.DataConnections["REST ClientLib"];

try
{
//change the url to point to the client folder

fq.FileLocation = this.ServerInfo.SharePointServerRootUrl.ToString() + "clients/c/docs/_vti_bin/listdata.svc/C_" + cliLib + "?$filter=Title eq '" + cliNo + "'";
fq.Execute();

}
catch (Exception ex)
{
LogActivity(ActionStr.ERROR, ex.Message);
}

Re: REST query fails for end users

Hilary Stoupa — Mon, 07 Aug 2017 16:20:27 GMT

You can extend the timeout in code for your data connection, yes - but I'm not sure why it would timeout for others and not for you? Did you try Fiddler?

Re: REST query fails for end users

Josee Sevigny — Sat, 05 Aug 2017 00:13:59 GMT

Hi Hilary,

Correct, this is a Filler form. I did create a separate test form and it worked fine. The error that comes back only presents the URL (which is the correct one), saying that it can't return the results. There is no proper error handling for this unfortunately. Is there any way to extend the timeout on this?

BTW, just to give you a bit more info...
The REST query targets folder in one of 12 possible SharePoint Document Libraries (hence not using a SharePoint List query because the URL is not modifiable at runtime).

The user types the Client Number (which is the same as the target folder) and a rule picks this up, edits the REST URL and executes. Then in principle, another field is updated with the found folder name but this never happens because the query fails.

I'm starting to think that I'd be better off exporting the PDF to a separate "fixed" library and building a new workflow to move it to the end target. At least it would be transparent to the end user.

Thoughts?

Re: REST query fails for end users

Hilary Stoupa — Fri, 04 Aug 2017 23:15:43 GMT

So - they aren't using a browser form, but IP filler? If you just create a simple test for with the same REST query (no code) do they have the same issue? Do they get an actual error message on why the query fails? Oh, if this is in Filler, you may want to try running Fiddler when they try the form, so you can get a look at what's happening.

REST query fails for end users

Josee Sevigny — Thu, 03 Aug 2017 16:58:05 GMT

Hi,

I built a REST data connection to validate the presence of a target folder prior to exporting to PDF.

The query works for me in and out of InfoPath.
The query works for end users outside of InfoPath.
The query FAILS for end users while in InfoPath.

I verified that the query uses the correct path and filter.
I verified that the end user has permissions to the target folder.

And obviously, because the following is to export to PDF, the form is Full Trust with a code signing certificate.

What am I missing?