InfoPath Dev

Actually, it seems to have been a SSO delay issue. Once I turned off SSO, the data returned immediately. Thanks.

There seems to be an initial delay when using the ExecuteSQLQuery command for the first time of the day in qRules. Is there any way to run a "warmup" script?

Yes , that's exactly what I did. It is an awesome thing to see as a non-programmer . :-)

Please ignore this post. I did not force a field which had a rule to query a data source to return data to the server. Once I did this, the ExecuteSQLQuery command ran -------------------------------------------------------  In the qRules User Guide, the PDF mentions that the ExecuteSQLQuery command is not browser compatible. But then on ...

Just in case someone runs into this same issue, check to make sure that the web.config in the QdabraWebService folder is referencing your SharePoint web application using the same URL defined in your alternate access mappings. It turned out mine wasn't fully qualified when Qdabra was first intalled. It wasn't an option.

It's been about a week. Any new directions?

Currently they are. I enter the same <server> into the Web Service URL prefix and the ShraePoint List URL text boxes. Can you describe to me the authentication workflow if Kerberos is turned on?

I'm trying to use the Qdabra Query SharePoint function with the Query Builder. I get an error when trying to connect:   Could not determine the schema.  Check your connection string and try again. Details: The query cannot be run for the following DataObject: DescribeListSchema InfoPath cannot run the specified query. The SOAP ...

I would like to mark this thread as closed since my original data source question was answered. I'll create a separate thread about duplicate promoted fields.

Have you had a chance to take a look at this?