Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

InfoPath question

  Asked By: Mindy    Date: Apr 08    Category: Sharepoint    Views: 1530

I'm not sure how many of you use InfoPath in conjunction with
SharePoint... I'm brand new to InfoPath myself, so I apologize if
this is a silly question.

I've created a form in InfoPath, the results of which are stored in
a SharePoint list. One of the fields in the form is a hyperlink -
however, there's no place (that I can see) to specify that the
content of this field should be a hyperlink, or a place in the form
to fill out display text for the hyperlink. You can do this in
SharePoint itself - but I haven't been able to figure out how to do
it in InfoPath. As it is, the SharePoint list displays the whole
long URL, and it would be much cleaner-looking if users could
specify alternate display text in the form.



10 Answers Found

Answer #1    Answered By: Gopal Jamakhandi     Answered On: Apr 08

In the top tool bar, (at least in my setup), I noticed there is an icon for a creating a hyperlink. The icon looks like the earth with a chain link in front.

If it is not there, you may need to play with your toolbar settings.

Answer #2    Answered By: Chantal Rosa     Answered On: Apr 08

I'm new to InfoPath, so here come the questions...

We are in the process of re-designing a legacy VB6 application. Our
goal is to replace all of the VB forms with web forms so our users
can access it from home, etc etc... We are planning on implementing
MOSS 2007 and WSS 3.0. I was wondering if hosting a bunch of
InfoPath forms would be a good idea, or a bad mistake.

Here is what we are trying to accomplish...

1. User fills out form  A
2. The form is validated
3. The chunks of data are sent to mulitple web services on
submission of the form
4. The web services do whatever with the data and store it in
various tables in a database
5. The user goes to Form B
6. Form B is pre-populated with some of data from Form A (which is
pulled from the database via web services)
7. The user fills out and submits Form B and the process continues...

What I am depicting is basically using InfoPath 2007 in place  of
creating a .NET web application that has multiple forms/multiple web

Is this a sound idea, or am I trying to use InfoPath for things
ASP.NET 2.0 is better suited for? (I've read that a best practice
was to host the InfoPath form in the same domain as the data source
you're using. However, this won't be possible for each form we
deploy. Is that a problem?)

Answer #3    Answered By: Kyla Eckert     Answered On: Apr 08

Sounds like a perfect application for InfoPath and SharePoint 2007 (new workflow
capabilities!!) to me (without putting a great deal of thought into it).

Answer #4    Answered By: Alisha Holmes     Answered On: Apr 08

It will also work with SharePoint Portal 2003 using Form libraries, Event Handlers, and Lists.

Answer #5    Answered By: Damon Garner     Answered On: Apr 08

You could always use the concat function on your stored  values i.e. concat(‘<ahref=”’, URL, concat(‘”>’, TITLE, ‘</a>’))

Just make sure that you define a TITLE and URL field.

Answer #6    Answered By: Percy Beach     Answered On: Apr 08

With a little more thought and planning on the how’s…you shouldn’t have a problem doing this in InfoPath (and SharePoint 2003 because they work together so well). Even without MOSS’s enhancements, I would try it out.

Answer #7    Answered By: Mary Adams     Answered On: Apr 08

My main point of concern with
using InfoPath forms is that they will be slow and not as useful
as .NET 2.0 web pages. We're going to be doing some serious data
manipulation and web service calls. Writing .NET code inside the
InfoPath form  is something I've not yet tested. Also, I've read that
some contorls cannot be used in the web browser, but haven't found
documentation on which specific controls. There's a lot of pluses to
using InfoPath, but I'm not sure if it can replace a bunch of .NET
web application.

I'm curious as to the pitfalls of doing such things.

Answer #8    Answered By: Laura Walker     Answered On: Apr 08

InfoPath can easily tie into any web services (I primarily just use the ones offered by SPS) and all the data sources that I’ve tried so far. I’m not sure about how extensively you can use .Net, but I know you can do some pretty advanced scripting. You can always write your own web service in .Net and tie it into the form(s). The benefit as I see it is that it is not truly running in a web browser…you can set how much access it has to other computers based on trust relationships too.

Pitfalls…not too many that I can see. I don’t know the details of the stuff you are working with and data you are trying to pull together, though.

Answer #9    Answered By: Kalyan Pujari     Answered On: Apr 08

I can tell you from experience that InfoPath client forms can definitely become
slow, it just depends on the complexity and design of the form. This MSDN white
paper explains the main causes for poor performance and how they can be remedied

As far as the browser-enabled forms in 2007, there's a rather extensive list  of
controls and functionality that isn't supported, some of them make sense (ink
features?) but some of them don't. There's a good list here
32.aspx) of many of the unsupported controls. I would add that XPath filtering
(such as in a dropdownlist) is not supported either. This really sucks when
you're trying to filter one dropdown based on the selection in another. anyway,
hope this helps.

Answer #10    Answered By: Katy Patton     Answered On: Apr 08

Hey guys wont BDC work here as well, as BDC doesn’t only retrieves data but through BDC apps we can also enter data using queries (I mean update queries), why use InfoPath for this?

One thing more what if we have to use SharePoint Lists for this, how can we use SharePoint Lists for this thing keeping in mind the new enhancements in V3 (actually I am trying to know the ‘how’?)

Any idea?.......

Didn't find what you were looking for? Find more on InfoPath question Or get search suggestion and latest updates.