-
Hello all,
I am a sharepoint expert who is not very experienced in InfoPath. Now i have a requirement to move a paper-form into sharepoint.
So these audit forms will be managed on sharepoint environment. I have had some infopath forms experience, but they were flat forms, that are 1-to-1 with the associated sharepoint list.
Now ...
-
Well, the form opens in InfoPath. Not in Browser.
The good news is..., I am able to fix this issue by changing few settings in IE.
Open IE-->Tools-->Internet Options--->Security--->Custom Level... ---> Initialize and Script Active X Controls not marked as safe for.....
Change the settings ...
-
Hi, infopath can be send data to excel chart. see this video, -> http://infopath.wordpress.com/2012/03/08/infopath-2010-sharepoint-2010-excel-services/
-
Thanks for your reply Anson. Btw, I have a new post. http://www.infopathdev.com/forums/p/24543/84869.aspx#84869
-
You rock!
your solution works. when I'm applying the decimal-compare - it gives me an error when clicking on the button: "some rules were not applied, unspecified error" .
10x a lot.
-
hey Jimmy,
The problem isn't with delete - that works perfectly in browser forms.
The problem is that preceding-sibling::my:Task doesn't work in browser forms, so the above concat'd command won't work to delete the current row as it's recommend for in this thread. Instead it needs to be changed to ...
-
This is rather puzzling. We've used qRules delete in browser forms and had success with it. I'm surprised that you ran into this behavior, but glad that you found a resolution.
-
Alright, I've resolved this.
Essentially, the expression above won't work in a browser form (the count will give 0, then add one, deleting the first row). However the following will produce the desired behaviour in a browser form:
concat("Delete ...
-
No, the postback happened correctly, and the row was deleted BUT the preceding sibling axis evaluated as zero, so the +1 then always deleted the first row.
I believe this is because it doesn't evaluate correctly in browser forms
-
Did the qRules Error field show an error? Have you double-checked that the button has Postback set to Always?