8.1 Calculated Column testing

Jaymer

I can't say I've had 100% success with the new CC.
Most times I give up and do something a different way.
This time I wanted this output:

but when my calculated was this: AS_STRING(Lead.DateLastActivity) + ' (' + Lead.LastActivityType + ')'

i got this:

Tried a format string but it didn't like that:

Once I saw what I had (showing the 12:00AM time), then it occurred to me:
CHARS_FROM_LEFT(AS_STRING(Lead.DateLastActivity),11) + ' (' + Lead.LastActivityType + ')'

Thats a lot nicer than having two columns. Hopefully this will continue to mature in future versions.

I give it the Clap !

tford

I think it would have worked if you used 'MM/dd/yy' instead of 'mm/dd/yy' (with M parameter in caps)

Jaymer

I did that first, then fell back to the lowercase M as a second test.

The docs do not show that AS=STRING allows a format parameter.
Also, if you look at the format masks for a date or timestamp field, they both upper and lower case M’s. The lowercase M‘s suppress the leading zero for months one through nine (I believe)

BLOMASKY

I didn't try it, but can you replace the comma with the @ sign AS_STRING(BO.attr@'mm/dd/yy')

bruce

tford

The docs do not show that AS=STRING allows a format parameter.
Also, if you look at the format masks for a date or timestamp field, they both upper and lower case M’s. The lowercase M‘s suppress the leading zero for months one through nine (I believe)

This is a tangent, but I keep this little cheat sheet to get date formatting the way I want it:

<<Current_Date, MMM d, yyyy>> - Jan 25, 2012
<<Current_Date, M/d/yyyy>> - 1/25/2012
<<Current_Date, MMMM d, yyyy>> - January 25, 2012
<<Current_Date, MMM d, yyyy>> - Jan 25, 2012
<<Current_Date, MMM d, yyyy>> - Jan 25, 2012
<<Current_Date, EEEE, MMM d, yyyy>> Wednesday, Jan 25, 2012
<<Current_Date, EEE, MMM d, yyyy>> - Wed, Jan 25, 2012