InfoPath Dev

I should add - do you have any other rules that are using the username function?

I have a field called FormName - and this concat(xdUser:get-UserName(), " ", translate(xdDate:Now(), "T:-", "")) is setting the value of that Field.  - It doesn't seem to be connected to QRules fields at all.  I have exported the source files and searched the manifest - the only place I am using Get-UserName is in this button.

Could it be something to do with permissions ? 

I am using the Qrules GetUserProfileByName on load so I have replaced the  xdUser:get-UserName(),  with xdXDocument:GetDOM("Get Current User")/dfs:myFields/dfs:dataFields/ns2:GetUserProfileByNameResponse/ns2:GetUserProfileByNameResult/ns2:PropertyData/ns2:Values/ns2:ValueData/ns2:Value[(../../../ns2:Name = "UserName") and (. != "")],  and re-published and it works fine .

I would take a new blank form, add some simple code to it (just set a field's value on load or something) and verify you can sandbox it. Then I'd add a rule to it to set another field to the username function - does it still sandbox? Just trying to see if we can narrow the issue down further.

Hi Hilary

I have a completely blank form - with two fields - I have set two rules on form load.  One to put "fred" in the first field, the second to put username() in the FormName field - that publishes to sharepoint and works in the browser.

I have made a copy of that form, and injected it with q- rules - I have not made any other changes.  I have publised to sharepoint successfully and I get the correlation error when I open the form.

I can send you the two forms if you want.

So, what I was wondering is if a code DLL that is NOT qRules also would cause the issue? That's why I suggested adding a little custom code to the form instead of injecting with qRules? Your original form that would not sandbox on your server would sandbox on our server, so it seems like it is a server difference of some kind, I'm just not certain what it might be.

Ok, so I have taken my base form - no qrules and no Username() and added some code  which sets a field to "newvalue" - boy was I rusty at that !  It is 2.5 years since i have written any code.

I published the form and it works fine.

I then included the username() function in one of the fields and re-published.  Again it publishes successfully but when you try and run it it gives a correlation error.

So in our set up it seems that if you use the username() function in conjunction with code (qrules or other) it fails.

The code on its own is fine.

The username() on its own is fine.

Oh interesting - thanks for checking that. I'm going to ask Jim if he's run into this before.

Here's what Jim suggested (and a question):

I would do as the exception notes and turn off custom errors to get more details in the logs.  Unfortunately, you need to know which site is being called so the appropriate SharePoint web.config can be modified.   An iisreset will be needed after the change.

If it is a test environment, no problems, but in a production environment it should be done during a maintenance window.

Were any recent updates applied?

Hi,

This is in production environment.

"Turn off custom errors"  where should I do that - Sorry probably a stupid question?

No recent updates applied - we are behind with updates - I think I remember us having a problem last year with the form which Jimmy developed for us - and we ended up having to publish it as an admin form.  I cannot guarantee - but my feeling is that that was the same issue.

Not a stupid question at all - the snippet of logs you posted said "For more information, turn off customErrors in the server's .config file." From what Jim said, I'm guessing that is the web.config for the SharePoint server? Is this a farm or a single server?