-
When the trial expires, qRules will stop working in your template. So if you were using qRules commands for logic in your form, those would cease to function. You can upgrade a form with the trial to the full version, however, and it will then continue to function correctly.
-
Just to make sure that the information is in the thread (and, of course, I agree with Patrick that a web service such as DBXL is a much better idea than building a form off a database), if Submit is disabled when you walk through the main data connection wizard, it may because of the data types in your table, or your form compatibility. ...
-
Hi --
You probably need to add .NET Programability Support to your InfoPath installation.Go to Control PanelSelect Programs and Features (or Add or Remove Programs, depends on the version of Windows you are using)Select your Office install and click ChangeSelect Add or Remove FeaturesUnder InfoPath, make sure .NET Programmability Support is set ...
-
Hi --
If you want to use the built in submit to SQL functionality, you took the correct initial steps (basing your form off a database).
I'm thinking you may have added controls bound to the wrong fields when you designed your form, however.
Here is a little tutorial you can walk through -- hopefully it will help you!
-
Well -- Add a secondary data connection to your form library where you have your submitted expense reports.
You can then use expression boxes to show the aggregated data. I've got a sample here that shows how to do this -- not by month, but the logic would be similar. The sample is also browser compatible, in case you need a ...
-
If you are promoting properties from your original form that has the info you need, you could use another form (or another view in this form) that uses the library your forms submit to as a secondary data source, and then aggregate the promoted data there....
EDIT: or you could also modify a view in your form library to show the aggregated data ...
-
Set oLastRow = XDocument.DOM.selectNodes("//my:myFields/my:Addrulegroup/my:addrulegroup/my:addruletable[a]")
is selecting a set of nodes.
Perhaps this:
Set oLastRow = XDocument.DOM.selectSingleNode("//my:myFields/my:Addrulegroup/my:addrulegroup/my:addruletable[a]")
would work better, then follow Potemkine's ...
-
You may not have gotten any help yet because your post is a bit hard to understand. I think you are saying that you published your form as an admin approved template, but when opened in the browser, your code does not run. This same code works in client, however.
If that is a correct assesment of your issue, are you getting any errors when you ...
-
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.
-
We've been emailing back and forth this week, but I wanted to add a final message to this thread just for the sake of some closure.
The reason custom submit messages were not displaying in the browser was because the submit action was not being called. That is, rules were calling submit data connections, but that isn't the same as having ...