InfoPath Dev

Environment:  Office 365 online + InfoPath 2013

Form Details:  200 text fields, 20 repeating tables, 20 check boxes with rules (trying), 14 calculated fields (too big?)

 

Issue:  Rules on checkboxes work until copied and pasted to others.  It's like I reached a size or some other type of limit. 

Rule:  Set field, set query field, query Secondary list 

Error:   

The SOAP response indicates that an error occurred on the server

Server was unable to process request ---> Unsupported expression 

 

 Any ideas? Not sure why rules would work on Box-1 and not on Box-2.

 

So - you are seeing an issue with rules you copied and pasted? You've double checked the rules to make sure InfoPath hasn't done anything "helpful" to them, like it sometimes does?

When pasted, the condition auto-updated to look at the correct check-box and I manually updated the actions to set a query field then run the query.

 

Condition: If check box is checked then... 

1.  Set Query Field

2.  Query Secondary Data Connection (SP List) 

 

Could any of these things cause this?

 - Form too big

- Too many defaults, rules on-load

 

What kind of things can cause this specific error? I'm not even sure where to look.  The rule is sooo simple.

 

 

 

To me, it seems like the query is causing the error (the SOAP in the error message). If you just temporarily disable the query what happens? If you disable some other rules, what happens?

Right now, I put the rules together piece by piece and tested.

 

Setting the query field is killing it.

 

I am setting a Query Field for a Secondary Data Connection (SP List) to the results of a query (SP List).  The same works on other check-boxes, just different fields on the data source?  The results from query-1that I am using to perform the 2nd query are not pasted in the main data connection.   

 

Does that help narrow it down? 

 

Is it setting the query field that is causing the issue? Or actually executing the query? Can you put the query and data fields for the list connection on the form, add a button that executes the query and experiment a bit to see what values cause an error? Sorry - I don't have any idea what is going wrong here, just trying to help you troubleshoot.

Hi Hilary, I have got the same issue "Unsupported Expression" while publishing the form, not getting any idea how to resolve this. But i think i have found the root cause why i'm getting this error. Please find below. We are using InfoPath in one of our project, there I’m trying to retrieve the secondary list data and setting that field’s data into the respective fields on the InfoPath form (using a button click action set field value rule). I have around 60 secondary list fields which I need to import to the InfoPath form. I’m getting an issue while publishing the InfoPath form, it looks like a SOAP error: Unsupported Expression. If I disable the ‘set field value action’ rule or if I decrease the number of secondary list fields from the InfoPath form then I can publish the form successfully. So I just want to know is there any limitations for importing number of secondary list field’s data or number set field values on an action rule in InfoPath form. Please let me know if you have any questions. Any help would be appreciated.