<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SharePoint Dashboard Conditional Indicators</title>
	<atom:link href="http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/</link>
	<description>Dashboard Examples and Business Intelligence Best Practices</description>
	<pubDate>Sat, 30 Aug 2008 00:50:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Joe</title>
		<link>http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/#comment-20527</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 14 Jul 2008 06:21:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/#comment-20527</guid>
		<description>Great tutorial, but I have one problem with the result. In one of my columns, I'm using a person's name, and even though I have the "presence indicator" turned off, once I make these changes in Sharepoint designer, the presence indicator shows back up. When it comes back, it's on the right side of the name rather than the usual left...

This is a problem because it distracts from the status indicators that were my goal in the first place. 

Any advice on how to remove these?</description>
		<content:encoded><![CDATA[<p>Great tutorial, but I have one problem with the result. In one of my columns, I&#8217;m using a person&#8217;s name, and even though I have the &#8220;presence indicator&#8221; turned off, once I make these changes in Sharepoint designer, the presence indicator shows back up. When it comes back, it&#8217;s on the right side of the name rather than the usual left&#8230;</p>
<p>This is a problem because it distracts from the status indicators that were my goal in the first place. </p>
<p>Any advice on how to remove these?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AnyChart</title>
		<link>http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/#comment-19969</link>
		<dc:creator>AnyChart</dc:creator>
		<pubDate>Mon, 04 Feb 2008 08:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/#comment-19969</guid>
		<description>You can also use charts to do the same:
http://www.anychart.com/blog/2008/02/04/add-interactive-charts-to-your-microsoft-sharepoint-portal/</description>
		<content:encoded><![CDATA[<p>You can also use charts to do the same:<br />
<a href="http://www.anychart.com/blog/2008/02/04/add-interactive-charts-to-your-microsoft-sharepoint-portal/" rel="nofollow">http://www.anychart.com/blog/2008/02/04/add-interactive-charts-to-your-microsoft-sharepoint-portal/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Standard Templates for MS SharePoint &#171; The Dashboard Spy</title>
		<link>http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/#comment-17942</link>
		<dc:creator>Web Standard Templates for MS SharePoint &#171; The Dashboard Spy</dc:creator>
		<pubDate>Sat, 10 Nov 2007 01:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.enterprise-dashboard.com/2007/07/27/sharepoint-dashboard-conditional-indicators/#comment-17942</guid>
		<description>[...] I pointed her to several SharePoint Dashboard videos on the dashboard screenshot blog - Dashboards By Example.  After we jointly studied a couple more dashboards done in SharePoint, our discussion turned to [...]</description>
		<content:encoded><![CDATA[<p>[...] I pointed her to several SharePoint Dashboard videos on the dashboard screenshot blog - Dashboards By Example.  After we jointly studied a couple more dashboards done in SharePoint, our discussion turned to [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
