Fields from filled out webbased InfoPath form becoming to a empty column in SharePoint - InfoPath Dev
in

InfoPath Dev

Fields from filled out webbased InfoPath form becoming to a empty column in SharePoint

Last post 08-05-2009 11:43 PM by stoepsel007. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 07-29-2009 06:43 AM

    Fields from filled out webbased InfoPath form becoming to a empty column in SharePoint

    Hello,

    I created a webbased InfoPath form (with C# code included) which actually works really fine. There are only two thing that make me angry.

    1. In the publishing wizard I can select the fields that I want to integrate as a column in my SharePoint InfoPath list. My problem now is that the columns are completly empty when I fill out a new form over the SharePoint form site. What is the matter with this form? Why is SharePoint not able to show the values coming from my form fields?

    2. Each time when I publish my form SharePoint creates new columns. Example: Original column: user; After the second release I get the colums: user, user_1 and so on

    Can you help me solving my problems?
    Thank you very much indeed!

     

  • 08-05-2009 06:12 PM In reply to

    Re: Fields from filled out webbased InfoPath form becoming to a empty column in SharePoint

    Hi:

    The first thing I would ask - how did you publish your form? Did you publish it using InfoPath directly to your SharePoint library or did you choose the option to admin-deploy it? You mentioned your form has code in it, and based on my experience, coded forms requires admin approval.

    Jo-Anne Alfafara
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™
  • 08-05-2009 11:43 PM In reply to

    Re: Fields from filled out webbased InfoPath form becoming to a empty column in SharePoint

     Hey Jo-Anne,

    Thanks for your reply. I choosed the option to deploy it as content type that needs admin aproval. But while developing the form I also decided to deploy it directly to the form library in order to speed up the publishing process. I think that's the mistake I made. After creating a new library where I published the form as content type everything works fine.
    What do you think?
    Greetings

     

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