-
Are you saying that only 255 characters are showing inside the fields in the form, or are you talking about the data in the fields showing in the form library?
If you changed those fields in the form from what they originally were, then that data may have been cut off. Does your form library have versioning turned on so that you can ...
-
Good, so my article was helpful? I thought it might be in this case. Just let us know how you put it all together when done...
-
Yes, those are its 3 nodes and is all it can do. You do not populate it with the UPS info when names are chosen or inserted. However, I do regularly auto-populate those 3 fields with UPS data sometimes so that people don't even have to select a name by doing this:
DisplayName = UPS PreferredName of either the logged-in user, ...
-
Bricey, I can walk you through this. You may get all you need just by reading my blog post here:
InfoPath - Get user information without writing code (extended)
That's how you get user profile info of people other than the logged-in user. I assume that since you're referring to the UPS in relation to your Contact ...
-
Notarian, I will test this tonight to confirm. As for your direct-to-SQL forms, why are those not using web services to submit to SQL?
Hopefully, you will be able to make your case for DBXL, since it is a great tool.
-
You don't have to copy data to show it in another view. You just copy the controls. The data is defined by the field itself, but you can have as many controls showing that data as you want.
However, if you need that data in a different part of your data schema, then you'll need to copy it, but I don't think that's what ...
-
You can't. That's a weakness of InfoPath and SharePoint - it is unfortunately not addressed in 2010 either. Luckily, Qdabra (the folks who run this site) have developed their own qRule that helps us do this, and it is part of the 2.0 suite that is soon to release. I have tested it and confirmed that it works on IP/SP 2007 ...
-
That means you have a rule issue or problem on your submit. Start with something very simple and work your way up. We can't tell you what the problem is just by giving us that error. We would need to see the entire way your form is structured - the web service you're using, the data connections, the submit method, the ...
-
I said that you could package the template as a solution, and that's what you did, not that it was impossible to do. I just did not know the steps to do so, and I definitely do not keep Visual Studio on my workstation where I build form templates, since I'm not a developer. Glad you found the method that works and thanks for ...
-
I don't believe there is a way to do it with 2003. Maybe if you had used the template part feature in InfoPath 2007. Not the best idea to still be using 2003.