-
We do, I think - I found a 2013 site with it on one of our servers at least - I'll save it as a template, then if it is too big to post here, I can use Hightail to get it to you.
-
I want to add a bit more information to this thread, since I had this same error message yesterday, and it would have helped me to have found some specific info on when this error occurs.
This error message occurs when a data field is set in a data source (via rules) and the data source has not been queried.
So - if you have a data connection ...
-
Yech, sorry about that. The easiest thing to do will be to deactivate the template and remove it, then upload the new template.
-
Do you know if the Sandbox service is enabled?
-
Great! That may also be why you weren't able to publish directly to the library as a sandboxed form.
-
Hi- may I see a copy of your form? You can attach it under the Options tab. I suspect you have injected it with the "admin" option in the injector - if that is the case, could re-inject it with browser and then try from preview again?
-
I'm not sure - I use the management shell for admin approving templates all the time - but not sure about direct library publish.
-
Okay - there are some limits which can be extended that can resolve this - here is a Stack Overflow thread: http://stackoverflow.com/questions/5722320/sharepoint-2010-sandbox-solution-timeout
This is the PowerShell script I use (run SharePoint Management Shell as admin) to extend these:
$spCodeService = ...
-
In general, if I get the warning that the form couldn't be verified, I'll assume it will have a publishing problem. If you run Fiddler while running the design checker (with the option to verify on the server) you can sometimes get more info about what is causing the issue (reading through the response details). I also sometimes check the ...
-
If you did not change the form schema, since you are opening the form from the library, you shouldn't have to attach your latest copy.