Qdabra Database Accelerator

Re: Should DBXL submitted form to SharePoint also be published to library?

Doreen — Thu, 19 Dec 2013 17:03:53 GMT

Actually I think I can modify ListViewWebPart on Page in SharePoint Designer to accomplish removal of New> New Document - but it's not a simple task.

I like your idea to create a redirection view if one trys to open. Thank you for the feedback, much appreciated!

Re: Should DBXL submitted form to SharePoint also be published to library?

ErnestoM — Thu, 19 Dec 2013 13:46:05 GMT

I don't know of a way to remove the "Add Document" or the "New" option from a SharePoint form library.

You could do some clever form design that switches users to a blank view with an error message ("You cannot create a new form this way.") if they open a blank form (i.e. if they click New or Add Document).

Re: Should DBXL submitted form to SharePoint also be published to library?

Doreen — Wed, 18 Dec 2013 15:39:03 GMT

What about permissions to the form? Right now I have a work flow that assigns permissions to the form in the library when it is submitted. Only the employee's supervisor and HR dept is granted permission to view a specific form in the library.

Edit: Actually I do not want to change where I store data from the form. I am happy with submitting form to SharePoint Library and data to SQL. I was looking for a way to prevent user from selecting New > New Document menu because it isn't allowed for this form.

It sounds like I still need the template "published" to open the xml stored in the library. I wasn't sure about that because I thought the xml was always going out to the web to retrieve the form template, not the library.

Re: Should DBXL submitted form to SharePoint also be published to library?

ErnestoM — Mon, 16 Dec 2013 20:36:43 GMT

Deleting the template.xsnn from the form library will definitely cause problems and not solve this issue.

The form library needs a form template (XSN) in it if it's going to open the existing forms (XML). Removing the XSN will not remove the New button - it'll just give the user some odd error message if they click New.

Plus removing the XSN will also prevent users from opening forms in that library, since there's no form template associated with the library.

Then (to make things even more complex) every time the doctype is saved from DAT, DBXL will push the XSN back into the form library.

I think the solution is to simply not have a SharePoint mapping, and not have a form library. The dashboard idea might be just what you need.

Re: Should DBXL submitted form to SharePoint also be published to library?

Doreen — Mon, 16 Dec 2013 20:09:02 GMT

Yes to #1, always.

Yes or No to #2. a user can and may open an existing form by navigating to the library (if they figure out where it is) but we are trying to reinforce a new procedure for this form only, to open new and existing form from their customized link in the email

Thank you for the Dashboard idea.

So to my original question, I would be okay with just deleting the template.xsn that I'd published to the library early on? That will not cause any problems?

Doreen

Re: Should DBXL submitted form to SharePoint also be published to library?

ErnestoM — Mon, 16 Dec 2013 18:40:31 GMT

It sounds like a SharePoint form library (and thus the mapping from DBXL) isn't needed at all:

1. Users won't navigate to the form library to open existing forms

2. Users won't navigate to the form library to create a new form.

Do correct me if I'm wrong.

Instead, just store the forms in DBXL, and create either an InfoPath Dashboard form, or use a data view - that is, IF you need to display the data. Here's an example of how to create a dashboard form: http://www.infopathdev.com/files/folders/other_subjects/entry88173.aspx

Hope this helps!

Re: Should DBXL submitted form to SharePoint also be published to library?

Doreen — Mon, 16 Dec 2013 16:13:37 GMT

It's client form, DBXL version Version: 2.7.2013.211 . This is our Employee Performance Review (EPR) form.

The form is opened by a supervisor from an email with the specific link/URL in it (e.g. http://servername/QdabraWebService/Forms/ID/XXX/template.xsn?EPRID=999). But technically one could just type in the URL into the browser if they knew what it was. A daily windows task process fires off a console app that does an employee review due date check. Depending on the date, an email is fired off to employee's supervisor with the link. Once created and filled out the form is submitted via DBXL to SharePoint library.If the form already EXISTS (has been submitted) it can be retrieved from the library otherwise the link is the only way to create it, initially.

A NEW form is never intended to be opened from the library NEW menu because it must be prepopulated with employee data. The top area of the form (employee data) is read-only so if a person opens a blank template from the library NEW menu they could not fill this section out and we don't want them to anyway. The data must be generated in a database first, then a link is emailed to supervisor with their employee's specific EPRID.

Re: Should DBXL submitted form to SharePoint also be published to library?

ErnestoM — Mon, 16 Dec 2013 14:02:55 GMT

How are the users going to open the form? Do they just type in a URL into the browser?

Is this a browser form or a client form?

What version of DBXL are you using?

Sorry for all the questions! I need to know more information before I direct you to one of our tutorials. Thanks.

Re: Should DBXL submitted form to SharePoint also be published to library?

Hilary Stoupa — Fri, 13 Dec 2013 22:24:45 GMT

Are you forms submitted to the library as well? Is the URL the forms are opened from the DBXL URL?

Should DBXL submitted form to SharePoint also be published to library?

Doreen — Fri, 13 Dec 2013 19:17:33 GMT

I have a form that is created via a url and only a url and is also submitted via DBXL. At early stage of development I published the form to SharePoint in traditional InfoPath way. Because of this user is able to select New > New Document from the library menu however this will result in user never being able to fill out the form because it requires the url to a specific bit of data.

I would like to remove the published form template from the SharePoint library so user cannot try to open a new form this way.

Will removing the form template from SharePoint library cause any problems with existing or future forms if I do so?