-
Is Form A an InfoPath form? if so, can't you publish it to SharePoint, promote all the fields to the SharePoint form library where it resides, and then create a data connection to that list for consuming its data? The data in Form B would always pull real time data from Form A.
If not, then what actually is your Form A, and why do ...
-
You can definitely do all of this with some nifty logic within InfoPath itself and a workflow built in SharePoint Designer (hopefully, you're not opposed to SPD). I could write up the entire solution, but that's a bit much for a forum. Instead, I will try to guide you with some basic tenets:
- Start by going to Tools > ...
-
Is this one of the working browser forms that you are viewing in the client, or did you make a new form that is for rich client only, and it is not working?
It definitely works in both. I would guess that if this is a new form, then you probably just got the syntax wrong on the Contact Selector nodes. They can be very finicky.
As a ...
-
Are you binding it to the repeating group (the row) as opposed to the element itself?
If you can show a screenshot of the properties of the list box when it's setup, then that would be great.
-
Wait. You're publishing each form as a content type, but then when asked to "Specify a location and file name for the form template," you are saving those templates directly into the form library where you later add them as content types? Are you sure that's what you're doing? You would typically create a ...
-
Ok, when you publish them as a content type, where are you choosing to save them as part of that publishing process (in the scenario when it doesn't work and points to your I: drive)?
-
I think that's the key. What exactly is I:\sharePoint Templates\formName.xsn?
How is that being associated with your form template in the SharePoint library? Is that a remnant from your own desktop...like a personal drive on a shared server or something?
How did you associate multiple forms with one library? Did you create ...
-
If you have MOSS Enterprise and use browser-enabled forms, then you can easily provide a link that takes users straight into the new form itself. If not browser-enabled, there isn't really a direct URL to opening a new form. You can provide a link straight to the form template (.XSN), but what this does is give the user a prompt ...
-
But what do you mean by "they can't open it"? That's what I'm asking. What _exactly_ happens?
Publishing to a share is not a good solution if you're using SharePoint. It should be published to SharePoint.
-
Definitely not normal behavior. I've never encountered that. What do you mean exactly when you say "now nobody can open the form3.xml'? They don't see it in the library? They see it, but they try to open it and get an error? What exactly happens?