<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Simple overlooked feature</title>
	<atom:link href="http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/feed/" rel="self" type="application/rss+xml" />
	<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/</link>
	<description>Tools To Get The Job Done Fast</description>
	<lastBuildDate>Sun, 19 May 2013 00:49:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Ethan</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-94</link>
		<dc:creator>Ethan</dc:creator>
		<pubDate>Fri, 02 Dec 2005 18:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-94</guid>
		<description>It would be really nice for my application if the (Date and User) stamp could itself be appended to the  _end_ of the multiple-choice text entry rather than the beginning.  I use a Pipeline field (pretty similar to a &#039;status&#039; field as mentioned by others above), and lots of my views sort by Pipeline.  This sorting gets completely screwed over when I start using the append/prepend function because it starts sorting by the (Date and User) stamp rather than the actual pipeline multiple choice options.

I agree with Anthony Rivera, a completely customizable append/prepend formula would be best... but absent that could we at least have an option to put the (Date and User) stamp at the end instead of the beginning of the field?
</description>
		<content:encoded><![CDATA[<p>It would be really nice for my application if the (Date and User) stamp could itself be appended to the  _end_ of the multiple-choice text entry rather than the beginning.  I use a Pipeline field (pretty similar to a &#8216;status&#8217; field as mentioned by others above), and lots of my views sort by Pipeline.  This sorting gets completely screwed over when I start using the append/prepend function because it starts sorting by the (Date and User) stamp rather than the actual pipeline multiple choice options.</p>
<p>I agree with Anthony Rivera, a completely customizable append/prepend formula would be best&#8230; but absent that could we at least have an option to put the (Date and User) stamp at the end instead of the beginning of the field?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ethan</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-18492</link>
		<dc:creator>Ethan</dc:creator>
		<pubDate>Fri, 02 Dec 2005 18:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-18492</guid>
		<description>It would be really nice for my application if the (Date and User) stamp could itself be appended to the  _end_ of the multiple-choice text entry rather than the beginning.  I use a Pipeline field (pretty similar to a &#039;status&#039; field as mentioned by others above), and lots of my views sort by Pipeline.  This sorting gets completely screwed over when I start using the append/prepend function because it starts sorting by the (Date and User) stamp rather than the actual pipeline multiple choice options.

I agree with Anthony Rivera, a completely customizable append/prepend formula would be best... but absent that could we at least have an option to put the (Date and User) stamp at the end instead of the beginning of the field?</description>
		<content:encoded><![CDATA[<p>It would be really nice for my application if the (Date and User) stamp could itself be appended to the  _end_ of the multiple-choice text entry rather than the beginning.  I use a Pipeline field (pretty similar to a &#8216;status&#8217; field as mentioned by others above), and lots of my views sort by Pipeline.  This sorting gets completely screwed over when I start using the append/prepend function because it starts sorting by the (Date and User) stamp rather than the actual pipeline multiple choice options.</p>
<p>I agree with Anthony Rivera, a completely customizable append/prepend formula would be best&#8230; but absent that could we at least have an option to put the (Date and User) stamp at the end instead of the beginning of the field?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Rivera</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-93</link>
		<dc:creator>Anthony Rivera</dc:creator>
		<pubDate>Wed, 09 Nov 2005 18:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-93</guid>
		<description>I use append/prepend quite a bit, but I&#039;m disappointed that you have no control over the tag for each post.  I think it would be great to have better customization options for appended text.  What would really be perfect would be a appeded forumla.  As an example for the way it currently formats the text the formula would be something like

[[date_modified] &amp; &quot;,&quot; &amp; [user] &amp; appended text]

I would like to be able to just show the date or just show the user or have the option to show neither one or whatever I wish.  Sometimes the date coupled with the username is information overload and takes up too much space, especially for one quickbase where I am using the field to track ticket numbers.  The date and username take up 3-4 times as much space as the apppended text.  This makes the view extremely cluttered.
</description>
		<content:encoded><![CDATA[<p>I use append/prepend quite a bit, but I&#8217;m disappointed that you have no control over the tag for each post.  I think it would be great to have better customization options for appended text.  What would really be perfect would be a appeded forumla.  As an example for the way it currently formats the text the formula would be something like</p>
<p>[[date_modified] &#038; &#8220;,&#8221; &#038; [user] &#038; appended text]</p>
<p>I would like to be able to just show the date or just show the user or have the option to show neither one or whatever I wish.  Sometimes the date coupled with the username is information overload and takes up too much space, especially for one quickbase where I am using the field to track ticket numbers.  The date and username take up 3-4 times as much space as the apppended text.  This makes the view extremely cluttered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Rivera</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-18491</link>
		<dc:creator>Anthony Rivera</dc:creator>
		<pubDate>Wed, 09 Nov 2005 18:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-18491</guid>
		<description>I use append/prepend quite a bit, but I&#039;m disappointed that you have no control over the tag for each post.  I think it would be great to have better customization options for appended text.  What would really be perfect would be a appeded forumla.  As an example for the way it currently formats the text the formula would be something like

[[date_modified] &amp; &quot;,&quot; &amp; [user] &amp; appended text]

I would like to be able to just show the date or just show the user or have the option to show neither one or whatever I wish.  Sometimes the date coupled with the username is information overload and takes up too much space, especially for one quickbase where I am using the field to track ticket numbers.  The date and username take up 3-4 times as much space as the apppended text.  This makes the view extremely cluttered.</description>
		<content:encoded><![CDATA[<p>I use append/prepend quite a bit, but I&#8217;m disappointed that you have no control over the tag for each post.  I think it would be great to have better customization options for appended text.  What would really be perfect would be a appeded forumla.  As an example for the way it currently formats the text the formula would be something like</p>
<p>[[date_modified] &amp; &#8220;,&#8221; &amp; [user] &amp; appended text]</p>
<p>I would like to be able to just show the date or just show the user or have the option to show neither one or whatever I wish.  Sometimes the date coupled with the username is information overload and takes up too much space, especially for one quickbase where I am using the field to track ticket numbers.  The date and username take up 3-4 times as much space as the apppended text.  This makes the view extremely cluttered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike NElson</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-92</link>
		<dc:creator>Mike NElson</dc:creator>
		<pubDate>Tue, 08 Nov 2005 16:32:40 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-92</guid>
		<description>Why doesn&#039;t it stamp the time as well?
</description>
		<content:encoded><![CDATA[<p>Why doesn&#8217;t it stamp the time as well?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike NElson</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-18490</link>
		<dc:creator>Mike NElson</dc:creator>
		<pubDate>Tue, 08 Nov 2005 16:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-18490</guid>
		<description>Why doesn&#039;t it stamp the time as well?</description>
		<content:encoded><![CDATA[<p>Why doesn&#8217;t it stamp the time as well?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keira Bromberg</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-91</link>
		<dc:creator>Keira Bromberg</dc:creator>
		<pubDate>Mon, 07 Nov 2005 06:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-91</guid>
		<description>I have been using this feature for long time for Status fields in situations like George mentions.  I usually call the Append-only one something like &quot;Status Update&quot; and use that for the Edit Record form.  I then create a formula field called &quot;Status&quot; that figures out the last status entered. For example, if the field is &quot;prepend&quot;:
Trim(Part([Status Update],3,&quot;[]&quot;))
I then can use the formula Status field in other formulas that depend on Status as well as for grouping Views. The only downside is if you want to prompt users for a specific Status choice at view runtime, it doesn&#039;t give you a multiple-choice list, just a type-in box.

</description>
		<content:encoded><![CDATA[<p>I have been using this feature for long time for Status fields in situations like George mentions.  I usually call the Append-only one something like &#8220;Status Update&#8221; and use that for the Edit Record form.  I then create a formula field called &#8220;Status&#8221; that figures out the last status entered. For example, if the field is &#8220;prepend&#8221;:<br />
Trim(Part([Status Update],3,&#8221;[]&#8220;))<br />
I then can use the formula Status field in other formulas that depend on Status as well as for grouping Views. The only downside is if you want to prompt users for a specific Status choice at view runtime, it doesn&#8217;t give you a multiple-choice list, just a type-in box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keira Bromberg</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-18489</link>
		<dc:creator>Keira Bromberg</dc:creator>
		<pubDate>Mon, 07 Nov 2005 06:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-18489</guid>
		<description>I have been using this feature for long time for Status fields in situations like George mentions.  I usually call the Append-only one something like &quot;Status Update&quot; and use that for the Edit Record form.  I then create a formula field called &quot;Status&quot; that figures out the last status entered. For example, if the field is &quot;prepend&quot;:
Trim(Part([Status Update],3,&quot;[]&quot;))
I then can use the formula Status field in other formulas that depend on Status as well as for grouping Views. The only downside is if you want to prompt users for a specific Status choice at view runtime, it doesn&#039;t give you a multiple-choice list, just a type-in box.</description>
		<content:encoded><![CDATA[<p>I have been using this feature for long time for Status fields in situations like George mentions.  I usually call the Append-only one something like &#8220;Status Update&#8221; and use that for the Edit Record form.  I then create a formula field called &#8220;Status&#8221; that figures out the last status entered. For example, if the field is &#8220;prepend&#8221;:<br />
Trim(Part([Status Update],3,&#8221;[]&#8220;))<br />
I then can use the formula Status field in other formulas that depend on Status as well as for grouping Views. The only downside is if you want to prompt users for a specific Status choice at view runtime, it doesn&#8217;t give you a multiple-choice list, just a type-in box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Carvill</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-90</link>
		<dc:creator>George Carvill</dc:creator>
		<pubDate>Sun, 06 Nov 2005 20:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-90</guid>
		<description>It does work, I just tried it. And it may be useful in some applications. However, it doesn&#039;t help me with my applications.

I use a field called &quot;status&quot; quite a bit. I would LOVE to be able to track who changed a status and when. However, I also use a lot of formula text fields that are based on the value in the status field. As soon as I change my multiple choice status field to append, my formulae are dead meat.
</description>
		<content:encoded><![CDATA[<p>It does work, I just tried it. And it may be useful in some applications. However, it doesn&#8217;t help me with my applications.</p>
<p>I use a field called &#8220;status&#8221; quite a bit. I would LOVE to be able to track who changed a status and when. However, I also use a lot of formula text fields that are based on the value in the status field. As soon as I change my multiple choice status field to append, my formulae are dead meat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Carvill</title>
		<link>http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/comment-page-1/#comment-18488</link>
		<dc:creator>George Carvill</dc:creator>
		<pubDate>Sun, 06 Nov 2005 20:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2005/11/03/simple-overlooked-feature/#comment-18488</guid>
		<description>It does work, I just tried it. And it may be useful in some applications. However, it doesn&#039;t help me with my applications.

I use a field called &quot;status&quot; quite a bit. I would LOVE to be able to track who changed a status and when. However, I also use a lot of formula text fields that are based on the value in the status field. As soon as I change my multiple choice status field to append, my formulae are dead meat.</description>
		<content:encoded><![CDATA[<p>It does work, I just tried it. And it may be useful in some applications. However, it doesn&#8217;t help me with my applications.</p>
<p>I use a field called &#8220;status&#8221; quite a bit. I would LOVE to be able to track who changed a status and when. However, I also use a lot of formula text fields that are based on the value in the status field. As soon as I change my multiple choice status field to append, my formulae are dead meat.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
