InfoPath Dev

Hello,

• I am working with qrules 3.3 (sharepoint 2010, infopath 2010) . 
• I created a quick test form in which one inputs an employee id, the form then fills in the employee's name, address, phone number, etc.
• This works fine in SP Designer 2010 preview. 
• I administratively published the form.
• Ran the form in browser mode on my SP server. 
• The form comes up, I fill in the employee number, the green chasing circle comes up as it retrieves data, then disappears without the data being filled in?
• Is there something I did incorrectly with publishing?

• -Bob

Hi Bob,

I can think of two ideas:

1. Since you're working in the browser, please make sure to set the controls (those that call qRules) such that their Postback setting is set to Always.

2. Display the Error/Success/Result nodes in the canvas to see if any messages come up that might give us a clue.

Thanks.

#1) Set to always per the documention.  there is only one field with qrules controls.  the field with the employee number.  it fills in all the other fields.

#2) I did drag out the secondary data source ( filterowssvr ) xml folder into the form.  On the preview it shows all my fields, in the browser I don't see it at all.  Is that what you mean (error/success/result nodes?)

thanks,

-B

The Error/Success/Result nodes are in the QdabraRules secondary data source, not in the FilterOwssvr data source. Can you display those in the canvas and see what error comes back when the command is executed? Thanks.

hmmm..

 in the SPD 2010 preview I get back

• Result = https://<stuff>
• Success = True
• Error = <null>

In the browser I receive

• Result = <null>
• Success = False
• Error = Failed to execute query

to be overly cautious I have set all fields to "always" under the browser form tab

Are you on SharePoint 2010? For ShP 2010 Browser forms, the URL needs an extra parameter: noredirect=true

I guess another option is that the form and the list are not on the same SharePoint instance/site, but I believe qRules would return a different error message in that scenario.

yes SharePoint 2010.

when you say the url needs an extra parameter, what url?  the one typed into the data connection for FilterOwssvr?  My current URL listed there is:

https://sharepoint.company.com/wf/_vti_bin/owssvr.dll?Cmd=Display&List=%7b344CC859-CF44-4A06-93B7-AFA6BCB1A6F6%7d&XMLDATA=TRUE

nvermind... found an example on your site...

It looks like you use that parameter: noredirect=true if I was running the form from a link.  I am running the form from within the form library by clicking on "add document"

form library and lookup list are in the same site https://sharepoint.company.com/wf

The data connection in your form was created using this link?:

https://sharepoint.company.com/wf/_vti_bin/owssvr.dll?Cmd=Display&List=%7b344CC859-CF44-4A06-93B7-AFA6BCB1A6F6%7d&XMLDATA=TRUE

Can you edit the data connection to use this link?:

https://sharepoint.company.com/wf/_vti_bin/owssvr.dll?Cmd=Display&List=%7b344CC859-CF44-4A06-93B7-AFA6BCB1A6F6%7d&XMLDATA=TRUE&NOREDIRECT=TRUE

....worked!

Thank you,

-B

One more question...

I am using qRules because I have a large list and it was not loading inside infopath.  The form was built and ready to go before I received all the data. 

Now I have gone through and removed all the references to list using the standard SharePoint data connection. but when I tested the form I received:

-------------------

InfoPath
A call to XDocument.GetDOM failed. The DataObject "oldbenefits" does not exist.

Error occurred during a call to property or method 'GetDOM'.

-------------------

I have seen this before and was able to clear it up by editing the manifest.  Of course I have named the sharepoint list that I read from and the data connection the same thing... "oldbenefits"  .  Now I am not sure where I can delete out the references to "oldbenefits"  

Is there a guide as to what sections in the manifest is ok to delete.  IE only the sections the reference the data connections and not the sharepoint list?

Most likely you still have a rule pointing to the old data source. You can see the rules in the manifest - and the XPath is probably different between the two data connections. Save a copy of your form first, of course!

Oh, and you may also be able to use the Rule Inspector (Logic Inspector in IP 2007) to help find this, if you want to use the UI.

ahh... when it rains it pours

When I go into the form library \ library settings \ advanced settings \ document template

I use to have a link there to 'Edit Template'.  That link has disappeared (it actually shows for a micro-second and dissapears).  I had this happen in 2007 but never connected that it may have had something to do with me messing around with the manifest files or the form itself.  Is this some sort of common issue?  I was never able to find a fix for it in 2007, is there a fix? 

Thanks for your help,

-Bob

I've never had this happen. Worst case, I suppose you could open your form library in Explorer view? The template is in the Forms folder.

went through the rule inspector and made sure there were no fields that had [Filtered] next to them, as any filed I looked up from the list with standard data connection had to be filtered.  I then saved the file, removed the reference to the data connection ' oldbenefits '  and tested.  Same error

 I then decided to try renaming the data connection to something other than the name of the sharepoint list 'oldbenefits'.  and tried the process again.  same error message

This time with the data connection renamed to something else, I thought I might have a better chance at cleaning up the manifest, until I get to the portion shown below.  I renamed the standard data connection from 'oldbenefits' to 'SIELOFF'  looking at the data below, I'm just not sure what I can extract out of this as it seems to reference both the old and new data connection within the same xsf:rule.  I have several sections like this

<xsf:rule caption="dependent1gender not blank" condition="xdXDocument:GetDOM(&quot;SIELOFF&quot;)/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Gender2 != &quot;&quot;" isEnabled="yes">
    <xsf:assignmentAction targetField="../my:SEC_DependentsYes/my:Dependent1Gender" expression="xdXDocument:GetDOM(&quot;FilterOwssvr&quot;)/xml/rs:data/z:row/@ows_Gender2"></xsf:assignmentAction>
</xsf:rule>

do i leave these sections alone, or should I delete out a portion before,after the reference to "SIELOFF"? 

I also have several views, each view will need to be visited as well, correct?

Thanks,

-Bob

The issue is with your condition on the rule - you can see it is checking your old data source in the rule condition. You should be able to just remove the condition:

For example. Then you can re-add the conditions in the UI if needed. Does that make sense?

You should not need to change anything in your views - unless you have conditional formatting in the view that used this data connection?