I have inherited a project and not 100% sure how it was configured to make it work.
There are 7 forms in this library. They're not templates for a document library that I'm aware, but when you use the web based "Filler", there are Submit and Close buttons at the top of the form (created by the original designer). The code for these forms basically takes 3 fields and migrates the data accordingly.
I have opened the forms from within the library using the desktop client and did the save button, works fine (stores correctly). However, I need to make it where web based editing works (I made sure to keep the checkbox ticked for this).
If someone goes in and attempts to load, there is a message saying that basically the code of it hasn't been approved in Central Administration. I go through the process of doing the upload form template and I'm getting some formatting messages:
1) Margins with auto which is the way it was initially.
2) header/footer, apparently can't be used in the browser version. Didn't add,
so shouldn't be a concern either.
3) (more concerning to me, though I do have upgrade form if it exists checked so maybe
a non issue) One or more form templates with this file name already exist on
the server. You may encounter problems from activation if a form template with
the same file name is already present in the site collection.
However, verification status = success and form template is ready to upload to the server (asides from the previously mentioned formatting messages + the existing file name one).
After that, I go to the activate for site collection area, activate, and the forms are listed as ready.
I have no intention of this being used as a form for a library/list, the goal is for them to edit data in the browser, click the submit button that was added, and it filter the saved file to a folder in the site. Presumably the codebehind solution for this handles it (if I do Edit in Microsoft InfoPath, it works as expected).
0 commentaires:
Enregistrer un commentaire