InfoPath Dev

 I played around with the rules a little more and I think I got it working. I had the rules in my submit button after the main database submit. If I move the main database submit after the Qdabra rules it works. Doesn't make sense why that would interfere with the SharePoint submit but it is working now. Thank You for you help!

What version of SharePoint are you using? I had another customer with an issue with this command (in SharePoint 2010), and I have found a logical flaw with it. I'll send an email to your forum address with a link for a new download with this fixed.

 Hi Hilary,

I want to follow up with you on the same thread.  It seems that the following rule is not working

concat("ChangeSubmitUrl /submit=ShPSubmit /url=", DocLibrary)

The form is submitting to ShPSubmit and I guess it is failing to submit the form to DocLibrary. I was reading the site and it looks like ChangeSubmitUrl command is no more supported. Is it replaced by something else?

 Noman

Hm, where did you read that? We should remove that comment, wherever it was. :)

The command still works, it is still supported. Please place the QdabraRules Error and Result node in the canvas, then execute the command. The nodes may return information on why it is failing in your scenario.

Thank you.

Also, be sure you submit after running the command - the command only changes the URL - it doesn't actually submit the XML.

 Hi Thanks for the quick response. I used the QRules tool and injected in the form. Now it works fine for me, but some of the end users complaining about an error

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}

Form template: http://intranet.dci.com/eng/apd/Form%20Templates/Tollgate%205%20Summary.xsn

InfoPath cannot open the selected form because of an error in the form's code.

System.Reflection.TargetInvocationException, mscorlib

 

System.Reflection.TargetInvocationException: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.InfoPath, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.

File name: 'Microsoft.Office.InfoPath, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'

   at System.Reflection.Assembly._GetType(String name, Boolean throwOnError, Boolean ignoreCase)

   at System.Reflection.Assembly.GetType(String name, Boolean throwOnError)

   at System.AddIn.AddInExecutorInternal.System.AddIn.IAddInExecutorInternal.Execute(String assemblyName, String className, IRemoteArgumentArrayContract initArgs)

   at System.AddIn.AddInExecutor`1.Execute(String assemblyName, String className, IRemoteArgumentArrayContract args)

   at Microsoft.VisualStudio.Tools.Applications.EntryPointAdapter..ctor(IRemoteArgumentArrayContract initArgs)

 

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

   --- End of inner exception stack trace ---

   at System.RuntimeMethodHandle._InvokeConstructor(Object[] args, SignatureStruct& signature, IntPtr declaringType)

   at System.RuntimeMethodHandle.InvokeConstructor(Object[] args, SignatureStruct signature, RuntimeTypeHandle declaringType)

   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

   at System.Reflection.ConstructorInfo.Invoke(Object[] parameters)

   at System.AddIn.AddInExecutorInternal.System.AddIn.IAddInExecutorInternal.Execute(String assemblyName, String className, IRemoteArgumentArrayContract initArgs)

   at System.AddIn.AddInExecutorInternal.System.AddIn.IAddInExecutorInternal.Execute(String assemblyName, String className, IRemoteArgumentArrayContract initArgs)

   at System.AddIn.IAddInExecutorInternal.Execute(String assemblyString, String className, IRemoteArgumentArrayContract args)

   at System.AddIn.AddInExecutor`1.Execute(String assemblyName, String className, IRemoteArgumentArrayContract args)

   at Microsoft.VisualStudio.Tools.Applications.Internal.ExceptionFilter.ExceptionFilterHelper.ExecuteCustomization(AddInExecutor`1 executor, String assemblyName, String className, IRemoteArgumentArrayListContract args, IExceptionFilterCallback callback)

   at Microsoft.VisualStudio.Tools.Applications.AddInImpl.AttemptInternalLoad(IAppDomainBindingContract appDomainBinding, String appBase, String configFile, PermissionSet topOfStackPermission, StrongName[] strongNameAssemblies)

 

Please advise,

Noman

 

Do your users all have InfoPath 2010 installed? Or are some of them using 2007?

 Most of them are using 2007 and some using 2010. When I injected I used the settings for InfoPath 2010.

 And I did notice those using 2010 don't get any error.

You'll want to make sure you save your form template as IP 2007 and use the settings for 2007 when you inject.

 And are you sure if I inject using 2007 settings it will work fine for Clients that have 2010 infopath installed?

Yes, it should work fine.

 Thanks guys I will try and let you know.

 Hello, I have a question. I used QRule injector for one of infopath form, which works fine. Now if I make any changes/updates in the form will I again have to do QRule Injector before I publish?

 Noman

No, you shouldn't have to re-inject. If you accidentally add code to your form, you can disable qRules, and then you'd need to remove code and re-inject, but in general re-injecting isn't necessary.