<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>(code segment) &#187; infopath</title>
	<atom:link href="http://oldblog.ideseg.com/category/sharepoint/infopath/feed" rel="self" type="application/rss+xml" />
	<link>http://oldblog.ideseg.com</link>
	<description>se acabarón las espinacas</description>
	<lastBuildDate>Thu, 26 Jan 2012 17:27:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>SharePoint &#8211; csegInfoPathViewer</title>
		<link>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer</link>
		<comments>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer#comments</comments>
		<pubDate>Tue, 09 May 2006 17:53:44 +0000</pubDate>
		<dc:creator>cseg</dc:creator>
				<category><![CDATA[infopath]]></category>
		<category><![CDATA[sharepoint]]></category>

		<guid isPermaLink="false">/post/SharePoint-csegInfoPathViewer.aspx</guid>
		<description><![CDATA[You can use now the row provider to select the infopath form (rememeber that the view need contains the ID field). The problems rendering fields with special characters is now solved. Also I added a cell consumer interface to get the ID from other webpart as csegRollUp&#160; In the properties you need add the XSL [...]]]></description>
			<content:encoded><![CDATA[<p><P>You can use now the row provider to select the infopath form (rememeber that the view need contains the ID field). <BR>The problems rendering fields with special characters is now solved. <BR>Also I added a cell consumer interface to get the ID from other webpart as <A href="http://inhttp:/www.ideseg.com/CategoryView,category,csegRollUp.aspx">csegRollUp</A>&nbsp;</P><br />
<P align=center><IMG src="http://oldblog.ideseg.com/content//csegInfoPathViewerF2.gif" border=0></P><br />
<P>In the properties you need add the XSL (see <A href="http://www.ideseg.com/SharePointCsegInfoPathViewerReleased.aspx">previous version</A>) and the name of the form library.</P><br />
<P align=center><IMG src="http://oldblog.ideseg.com/content//csegInfoPathViewerF1.gif" border=0></P><br />
<P>If you can´t display the infopath form, check if&nbsp; you can get the XML from the server using the form Url. Some users are using a WSS environment where they don´t use DNS to resolve the url where WSS is located, they are using an entry in the hosts file. In this case the server can´t resolve the Url where the form is located. To solve this issue you can add the host name in the hosts file of your server. </P><IMG src="http://oldblog.ideseg.com/content//save_16.gif" border=0>&nbsp; <A href="http://oldblog.ideseg.com/content//csegInfoPathViewer12.zip"><STRONG>csegInfoPathViewer12.zip (15,11 KB)</STRONG></A></p>
]]></content:encoded>
			<wfw:commentRss>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer/feed</wfw:commentRss>
		<slash:comments>2673</slash:comments>
		</item>
		<item>
		<title>SharePoint &#8211; csegInfoPathViewer released</title>
		<link>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer-released</link>
		<comments>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer-released#comments</comments>
		<pubDate>Fri, 07 Apr 2006 15:20:56 +0000</pubDate>
		<dc:creator>cseg</dc:creator>
				<category><![CDATA[infopath]]></category>
		<category><![CDATA[sharepoint]]></category>

		<guid isPermaLink="false">/post/SharePoint-csegInfoPathViewer-released.aspx</guid>
		<description><![CDATA[Finally I have a first version (0.99) of my InfoPath viewer, first I want give thanks to my friend Gustavo, for testing the preliminary version and to make as always good suggestions. Installation stsadm -o addwppack -filename csegInfopathWebPart.cab -globalinstall&#160; (use -force if you have installed the preliminary version) Use a) Create a view in your [...]]]></description>
			<content:encoded><![CDATA[<p><P>Finally I have a first version (0.99) of my InfoPath viewer, first I want give thanks to my friend <A href="http://www.gavd.net/servers/"><STRONG>Gustavo</STRONG></A>, for testing the preliminary version and to make as always good suggestions.</P><br />
<P><B>Installation</B></P><br />
<P>stsadm -o addwppack -filename csegInfopathWebPart.cab -globalinstall&nbsp; (use -force if you have installed the preliminary version)</P><br />
<P><B>Use</B></P><br />
<P>a) Create a view in your Form Library webpart containing the identifier of the list (the ID field). </P><br />
<P>b) Create a new webpart page, and insert the FormLibrary webpart and csegInfoPath webpart. </P><br />
<P>c) In the FormLibrary webpart select the view that contains the ID field, you need this view to connect with csegRollUp.</P><br />
<P>d) In the FormLibrary webpart menu select, &#8220;Conections&#8221; -&gt; &#8220;Send row to&#8221; -&gt; &#8220;csegInfoPathViewer&#8221; when prompt for field use the ID field.</P><br />
<P>e) Now fill the csegInfoPathViewer properties, you need specify the form library list name in the &#8220;List Name&#8221; field and put the XSL in the field XSL. (You can extract it from the infopath solution file, rename it as a .cab file and extract the xsl, then copy the content into the xsl property)</P><br />
<P>f) Now select an item and you can view the form in the csegInfoPathViewer.</P><br />
<P align=center><IMG src="http://oldblog.ideseg.com/content//csegInfoPathViewer.jpg" border=0></P><IMG src="http://oldblog.ideseg.com/content//save_16.gif" border=0>&nbsp;<A href="http://oldblog.ideseg.com/content//csegInfoPathViewer1.zip"><STRONG>csegInfoPathViewer.zip (8,44 KB)</STRONG></A></p>
]]></content:encoded>
			<wfw:commentRss>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer-released/feed</wfw:commentRss>
		<slash:comments>2403</slash:comments>
		</item>
		<item>
		<title>SharePoint &#8211; csegInfopathViewer test release</title>
		<link>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer-test-release</link>
		<comments>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer-test-release#comments</comments>
		<pubDate>Tue, 14 Mar 2006 19:12:43 +0000</pubDate>
		<dc:creator>cseg</dc:creator>
				<category><![CDATA[infopath]]></category>
		<category><![CDATA[sharepoint]]></category>

		<guid isPermaLink="false">/post/SharePoint-csegInfopathViewer-test-release.aspx</guid>
		<description><![CDATA[This is my first attempt&#160;to do an infopath viewer webpart, this is only a test version that run. To run this webpart you need fill the properties, list (form library) field name of the field that you want show in the combo box to select the form and the xsl to render it. (You can [...]]]></description>
			<content:encoded><![CDATA[<p><P>This is my first attempt&nbsp;to do an infopath viewer webpart, this is only a test version that run. To run this webpart you need fill the properties, list (form library) field name of the field that you want show in the combo box to select the form and the xsl to render it. (You can extract it from the infopath solution file, rename it as a .cab file and extract the xsl, then copy the content into the xsl property) </P><br />
<P align=center><IMG src="http://oldblog.ideseg.com/content//csegInfoPathViewer_beta1.gif" border=0></P><br />
<P align=center><IMG src="http://oldblog.ideseg.com/content//save_16.gif" border=0>&nbsp; <A href="http://oldblog.ideseg.com/content//csegInfopathViewer.zip">csegInfopathViewer.zip (6,82 KB)</A>&nbsp;</P><br />
<P align=center>&nbsp;</P></p>
]]></content:encoded>
			<wfw:commentRss>http://oldblog.ideseg.com/2006/sharepoint-cseginfopathviewer-test-release/feed</wfw:commentRss>
		<slash:comments>2737</slash:comments>
		</item>
	</channel>
</rss>

