-
It seems unlikely you made any manual changes to the XSL then - can I take a look at your template? You should be able to attach it in a reply under the Options tab....
-
Wow - that is kind of weird - you didn't make any modifications to the XSL files in the form?
Under the Publish page in the backstage, you can export the form as source files - from there, you can open and examine the XSL for the views to see if you can find the problematic HTML.
-
You certainly can - You'll want to make sure those names are unique tho. :)
-
Hi - you'll want to add the name field as an attribute to the File node and then use the relative path in the command. See attached. :)
-
Did you re-inject the form when you saved it as IP 2013? It had been 2007, right? Or did you completely re-create the form?
I'm going to ask a colleague of mine to take a look at this thread - he is out this week, but can hopefully chime in on Monday.
-
Yup, just click Ignore and IP should use the compiled DLL that is in the form's source files. If you ever need to see what is in the code file, try a decompiler like IlSpy - that will let you recreate the code if needed.
-
Okay, so it should be compatible with SharePoint 2013. I think the next step would be to check the SharePoint log files and see if there is any useful info there. Maybe put the useWebServices field on the form, so you can try submitting both ways and then check the log files after your attempts.
-
What version of qRules are you using?
-
I'm guessing the issue is with the new SharePoint Server. What is the error if you DON'T set use web services to true?
-
Are there commands available only for Admin approved injection you need to use? You should be able to admin approve your form that is injected with Browser & Sandbox
Based on the error, however, you may be able to set the form to full trust prior to admin deploying...