Custom DIP not pulling data from Web Service - InfoPath Dev
in

InfoPath Dev

Custom DIP not pulling data from Web Service

Last post 04-19-2011 08:58 PM by Karthick. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 04-18-2011 07:24 AM

    Custom DIP not pulling data from Web Service

    I have a Custom Document Information Panel developed in InfoPath - within which I am calling a Web Service to return a date value from the server. The DIP when opened independently works fine, that is, it calls the Web Service and returns the relevant data.

    But when the DIP is published on to the content type and then a new document is created from the SharePoint library, the DIP says " unable to load ".

    This is the issue that is being shown:


    Document Information Panel cannot open a new form. The form template associated with this form was moved or cannot be accessed. The form template "Template 1" on your computer has the same form ID as the template associated with the form, but it is from a different location.

    Location of the associated form template : http://sharepointserver/SharedDocuments/Forms/ContentType1/template1.xsn

    Original location of the form template on your computer: file:///c:\Documents\Template1.xsn.

    Make sure you can access the location of the sasociated form template and try opening the form again. If that does not work, ask the form author to update the form.

    Karthick
    SharePoint Enthusiast
    http://karthickmicrosoft.blogspot.com
    Filed under:
  • 04-19-2011 03:33 PM In reply to

    Re: Custom DIP not pulling data from Web Service

     Is this something that can be manually edited in the manifest before publishing to SharePoint? I haven't worked with DIPs at all, so I don't know how/where the details for them are stored--I'm assuming in the manifest.

  • 04-19-2011 08:58 PM In reply to

    Re: Custom DIP not pulling data from Web Service

    Yes Greg, thanks, this is what I did - renamed the .xsn to .cab, extracted - removed the PublishURL from inside the manifest file, re-built the cab, renamed to .xsn and put it inside. It works fine now. I also got access denied issues, for which I had to add not only the SharePoint URL to the Trusted Sites, but also the Server Running the Web Service into Trusted Sites. Surprisingly, it didn't work if added to Local Intranet Sites.
    Karthick
    SharePoint Enthusiast
    http://karthickmicrosoft.blogspot.com
Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.