I have a process that is using an infopath form which is required to be rendered in the browser, as not everyone has the client.
The infopath form has several data connections, which use UDC files in a data connection library to connect to web services to retrieve information.
I developeed the process, and have managed to test it and it works fine in the development environment (server in development environment is http://sptest)
I have now moved the process to the production environment (server http://spprod), and found that the form will not open in the browser - only in the client.
After much tearing of hair trying to work out why, I managed to determine that when I deploy the form to production, it is still trying to use the data connections from the development server - ie it is looking for the data connections at:
http://sptest/data connections
rather than at:
http://spprod/data connections
This is not allowed in forms services, as the data connections udcx files must be in the same site collection.
Am I doing something wrong here? How should I set up my data sources in an infopath browser form so that they function correctly when moved to production?
I have read through this post http://k2underground.com/forums/thread/21651.aspx, which was helpful, however I am still getting errors with my data sources which I can't figure out.
This is an urgent issue for me, as this is due to be live on Monday morning (it is now late Friday afternoon). If anyone can assist me with this it would be very much appreciated!
Thanks in advance!!
Infopath Browser Forms and Data Connections
+9
+4Hi arduk,
I posted a similar question 1 week ago which is unanswered so far (http://www.k2underground.com/forums/post/24320.aspx). Filed also a request to the support team which has to be looked at, at their lab.
So, for the meantime I found a workaround (which is not satisfying in the long run, but works in the meantime).
- Create a normal data connection file in your development environment and save it in the K2 BlackPearl Data Connections library (this custom udc file will NOT! be included in your deployment package, so you have to copy it manually).
- copy the udc file to the production environment
- open a text editor and hack in the values for your production environment
- deploy the altered udc file to your K2 BlackPearl Data Connections library at your production environment - voila
Regards,
DD
+9Hi DD,
Thanks heaps for your suggestion - that workaround sounds like it might work for me in future - I suspect that this is a bug with K2 though.
I didn't use your suggestion in this case (I have another solution - see below), as it would have meant me removing and re-adding all of my data connections in the form - the form is quite complex, and I was doing everything I could not to have to do that!
My solution (more of a dodgy workaround to help me meet a tight deadline) was to extract the source files from the form as described in the post that I linked to above. I then edited the data connection values, and re-published the form back to the document library. Far from ideal, but it worked.
Sorry, I had actually tried this before posting above, but had thought that it hadn't worked, as I had another unrelated error which I only found after going back over the sharepoint logs very carefully.
Hope this helps someone out in future - at least until K2 sort this out.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.