You searched for the word(s): 12
-
Oh, I see. It's a browser form. You may have just hit a performance limit for InfoPath browser forms. It's 100 rows x 5 fields per row?
-
Interesting - I'll check with out test team and see what scenarios they tested the command with.
-
Would you be able to attach that simple, test form to your next reply? (You can attach via the Options tab). We'd like to take a look.
Thank you.
-
This works great in preview.
I had to add 100 rows. But It works well.
The published version in SharePoint hangs up the form.
I have the following Xpath code on an index field that shows a row number.
count(preceding-sibling::*/DeliverableID) + 1
Like I said, everything works well in preview. hangs up the form when I load the view in ...
-
I haven't found a good answer to the error message:
This form cannot be opened because it requires the domain permission level and it currently has restricted permission. Contact the form author to resolve the issue.
I have the form set to "Domain level", but why are some users not able to open it.
-
Hilary, as usual you have an answer for my every issue, well just about! :)
I do not know why I didn't think of just publishing a new content type. Now I see why this is the prefered method when publishing a form.
After I'm dont hitting my head against my desk I'll do that, and thank you very much. ...
-
-
I finally found the answer on this forum...
-
Getting it both in Preview and after publishing. The form and the library are on the same SharePoint site. I even set up a new form library on the site and published a test form there injected with qRules 4.0. The test form only has one user field, Command, which I use to set the qRules command field. I get the same result ...
-
Are you getting this error from preview? Or after publish? If published to the same site as the location you are deleting from, the form can be domain trust. But if not, it would need to be full trust.