Duplicate a form in another site - InfoPath Dev
in

InfoPath Dev

Duplicate a form in another site

Last post 03-08-2006 01:29 PM by StephenM. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 03-07-2006 07:37 PM

    • StephenM
    • Not Ranked
    • Joined on 02-16-2006
    • Australia
    • Posts 10

    Duplicate a form in another site

    Currently I have a site with a subsite. In the subsite is an infopath form library where people can fill it in. Once it has been approved I need it to be copied up to the parent site.

    Currently I do this by another submit connection to publich it to the parent site. It works fine.

    It stops working however when I apply the security IE most people can only see the approved form in the parent site and the sub site has been locked from them.

    The issue is as the form has been copied to the parent site it seems to contain a reference back to the sub site I think this is in the publishURL in the manifest. So when a user opens the form for view it tries to access the subsite form library, there are no data connections that reference it at all.

    Anyway can anyone think of a solution or another way to accomplish this cheers

    MSN and email [email protected]
  • 03-07-2006 10:22 PM In reply to

    Re: Duplicate a form in another site

    Hi Stephen,
    The solution template must be downloaded so that the form can be displayed. That's essentially like giving them read-only access to the form's XSN file (which they need to open the XML form). So, why not just lock them from edits? If you have other info on the sub site which is sensitive, consider publishing the form to a separate folder and making that read only.
    Patrick Halstead
    Project Manager at Qdabra
  • 03-08-2006 01:29 PM In reply to

    • StephenM
    • Not Ranked
    • Joined on 02-16-2006
    • Australia
    • Posts 10

    Re: Duplicate a form in another site

    quote:
    Originally posted by Patrick Halstead

    Hi Stephen,
    The solution template must be downloaded so that the form can be displayed. That's essentially like giving them read-only access to the form's XSN file (which they need to open the XML form). So, why not just lock them from edits? If you have other info on the sub site which is sensitive, consider publishing the form to a separate folder and making that read only.



    The access in the top level site is view only already I really didnt want to keep enabling security in the subsite for those people, but to get around my problem I may have to.

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