Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Calculated Field Question

  Asked By: Wendy    Date: May 29    Category: Sharepoint    Views: 1667

A question was posed to me regarding a calculated field that she has
incorporated into a custom list. The result should be for a email
message to be generated as follows.

="mailto:"&[Recipient Last Name:]&"?subject=CI%

The problem I am having is that the message dies at "award. Http" It
will not reference the link to amazon. This i believe stems from the
fact that this shows up as 2 links

="mailto:"&[Recipient Last Name:]&"?subject=CI%


What am i missing here. What will bring these together so that when
the email is generated the html link will reside in the body of the



8 Answers Found

Answer #1    Answered By: Darrius Whitfield     Answered On: May 29

Taking a stab but the url ends up being over 255 characters. Another thing
too try is to use blank spaces instead of %20.

Answer #2    Answered By: Adrienne Greene     Answered On: May 29

Not sure why the url size would matter in this situation. I understand the 255 char limitation but this is simply a link  that will be pushed to outlook.

Answer #3    Answered By: Joshuah Huber     Answered On: May 29

Anyone else have any insight on this?

Answer #4    Answered By: Laura Walker     Answered On: May 29

It appears to me that this is a simple character limitation of the one-line calculated  field being used. The underlying data type will only store a certain number of characters, regardless of the content.

Answer #5    Answered By: Keenan Whitehead     Answered On: May 29

I will try to have them shorten the string and see if that does fix the issue.

Answer #6    Answered By: Gopal Jamakhandi     Answered On: May 29

This turned out not to be an issue with the length of
the message  but a simple bonehead character that was being
placed.... apparently http:// had to be written as http%3A// in
order to join the two displaced sentences together.

Answer #7    Answered By: Dameon Dejesus     Answered On: May 29

I think it is the " mark that precedes the HTTP. It looks like you're breaking the string up in the middle. Try changing it to a ' instead.

Answer #8    Answered By: Tejaswani Barve     Answered On: May 29

Removing the :// brings everything together. When I readd the :// it once again seperates.

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