Attaching form that uses code - InfoPath Dev
in

InfoPath Dev

Attaching form that uses code

Last post 08-28-2014 12:32 PM by Fdcctx. 11 replies.
Page 1 of 1 (12 items)
Sort Posts: Previous Next
  • 08-27-2014 09:10 AM

    Attaching form that uses code

    Hello,

    I have a form that is using a custom task pane. My issue is that not all user can open the file. Users recieve this error - "Forms that require the domain permission level contain features that access information on a network, such as data connections, linked images, and code." I tried changed the security to resiticed, but then the task pane does not show up. I was thinking to try and use the code as a resource fie (that way it is in the form), but I am not sure how to do that. So I think I need some help in setting this up. Ideally, this will be going to a SharePoint site, but in our inital phase, we want to have the form sent to an e-mail so that it follows our normal process with the new form before utilizing a SharePoint site. Any help would be appreciated. I attached the file in case that would give a better idea on what I mean by task pane.

    Thanks,

    Frankie D.

  • 08-27-2014 09:12 AM In reply to

    One more- I also tried removing the code (expected the task pane not to work) but looked to work fine. However users still recieve the error above. I attached the one with the removed code (at least removed from Form Options->Programming and clicking remove code.

  • 08-27-2014 09:14 AM In reply to

    Re: Attaching form that uses code

    It definitely needs to be published at least as Domain trust. Your users are opening the form from the published location? I ask because I see that it is published to a personal SharePoint site. Is the SharePoint server in their local intranet? From your post, it sounds like some users can open the form and some cannot, is that correct?

    Hilary Stoupa

  • 08-27-2014 09:39 AM In reply to

    Re: Attaching form that uses code

    The SharePoint site is just a test for me to see how it works. It will eventually go to a team SharePoint site - but we are not there yet. So that was just a test. We do have the form saved as a file on a SharePoint site, but this is so users can access the file from a link that is on a different site (if that makes sense). But yes, basically, most users are not able to open the form. I can and another person can, but the majority of users cannot.

  • 08-27-2014 09:48 AM In reply to

    Re: Attaching form that uses code

    I wouldn't expect it to work when saved as a file - try publishing it to a library and then providing the users with a link to the library the form is published to.

    Hilary Stoupa

  • 08-27-2014 10:16 AM In reply to

    Re: Attaching form that uses code

    If it is published, could it still work for a user to open from a link on a different site? The idea right now is to keep our normal process before incorporating SharePoint. The file is just saved on SharePoint for the link to reference the file. I'm not sure how to do that with a published form. But either way, I tried for a user to open the form from being published to the site, and an error message occurs (on the form with code not taken out). I also tried with the one with code removed, and when the user clicks on new - a screen opens that says "Form has been closed". So not sure what that means.

  • 08-27-2014 11:42 AM In reply to

    Re: Attaching form that uses code

    As long as the user has access to the site. You could publish it as a content type, too, if you don't want a form library created. Are you intending this be used a browser or a filler form?

    Hilary Stoupa

  • 08-27-2014 12:21 PM In reply to

    Re: Attaching form that uses code

    Well - a filler form as I read you can't use the custom task pane in a web browser form.

     One thing I am thinking (but can't find out how) is can I have the Project Loaction for the code be placed on the SharePoint site? If so, how do I reference that path in the location section? It's a thought, but I think that is where I am having the problem - even with the form where I removed the code. I could be wrong, but that's the only thing I can think of that would be causing the issue.

    Just to give more info on what I am seeing - I tried to open an older version of this form (I save periodically to keep my progress), and I recieved the error as decsribed - "This form cannot be opened because it requires the domain permission level and it currently has restircted permission. To fix this problem, open the form from the location it was published to - gives the path." I click show details and get - "Forms that require the domain permission level contain features that access information on a network, such as data connections, linked images, and code."

     But now when I open in design mode and save (don't change anything) it prmpts as a new file. So I saved over the original and closed. I am then able to open the file. I'm not sure if there is a connection,but just providing more info in case it helps identify the issue.

     

  • 08-27-2014 12:25 PM In reply to

    Re: Attaching form that uses code

    Sorry, of course it is filler. So - if you publish the form (with the security set to domain), are your users able to access from a link? I'm sorry, I'm having trouble understanding if you tried that yet.

    Hilary Stoupa

  • 08-27-2014 01:04 PM In reply to

    Re: Attaching form that uses code

    No worries - I think I am all over the place in my description as well. With my peers, they are opening it from my network folder. However, other users won't have access to our specific folders. So that's why we are trying to save it to a SharePoint site (as a document) to be able to be accesed there through a link on a general site, so the users don't have to go to the SharePoint site the file is on (yet). However, we want to make sure people can open the file before making it a link (because I am thinking it should work just like opening it up from the newtork drive/SharePoint site). And (of course) the person who is creating the link for other users cannot open the form. So I want to make sure people can open it first before getting the link together.  

    Just some more info to provide (incase it makes things more clear) - This SharePoint site we want the file housed, houses a few other InfoPath forms (but more basic forms). This is the first where we get more elaborate with InfoPath and include the task pane as a help screen. I did this way back when with a different team using 2007 InfoPath and SharePoint and want to adapt that process - but now using 2010. The site we house the current forms is a 2007 SharePoint site, but we will use a 2010 site once we are ready to intergrate this file and SharePoint.

  • 08-27-2014 02:07 PM In reply to

    Re: Attaching form that uses code

    What I am trying to say is that in order to open correctly, InfoPath form templates need to be published. If you publish it to your SharePoint site, you can still provide a link that will open the template. They do not have to go to the site itself.

    Published to a library, the form template's URL would be:

    http://server/site/library/Forms/template.xsn

    Obviously the server/site/library bit is just a placeholder.

    Here is more information on publishing InfoPath templates: http://office.microsoft.com/en-us/infopath-help/publish-a-form-HA101783381.aspx

    Hilary Stoupa

  • 08-28-2014 12:32 PM In reply to

    Re: Attaching form that uses code

    I appreciate the help. we did find the issue (or potential issue). Some users have Chrome as thier web browser. Apparently Chrome acts funny with InfoPath. When the user opened up the file in Internet Explorer rather than Chrome - the file opened up fine and all was glorious. :) But when using Chrome - either an error comes up or a screen that says "File has been closed" appears. But now that we have instructed to open in Internet Explorer and not Chrome everything is working as expected. Thanks again for your help with this.

    Frankie D.

Page 1 of 1 (12 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.