We’re rewarding the question askers & reputations are being recalculated! Read more.
10

For some reason, Salesforce does not allow you to make a number of types required. It's no use asking why. Workaround: make a validation rule that checks whether this field is filled.


6

If you just change the Field Type from Rich Text to Long Text, Salesforce will take care of stripping out HTML tags while converting line breaks into new lines. Just go to Setup and find your field, then click "Change Field Type". When you select "Text Area (Long)", Salesforce will present a "Field Conversion" screen which asks you what you want to do with ...


6

The JSENCODE Visualforce function will escape the line feeds and other unsafe characters: summary.Discussion_Topics__c = '{!JSENCODE(Event.Description)}'; This works in custom button JavaScript too e.g. in a custom "Execute JavaScript" button on Account: var d = '{!JSENCODE(Account.Description)}'; alert(d);


6

You cannot search for wildcards at the beginning of a word, but this doesn't mean you can't search for any word anywhere within a long text area. Let's use an example string with some search terms: "The quick brown fox jumps over the lazy dog," said I. First, we need at least two characters, so we can't do this: FIND {I} ... Also, we can't search for "...


6

<apex:outputText value="{!SUBSTITUTE(JSENCODE(loo.Note_SA__c),'\n','<br/>')}" style="white-space:pre;" escape="false"/> change this into this <apex:outputText value="{!SUBSTITUTE(JSENCODE(loo.Note_SA__c),'\\\n','<br/>')}" style="white-space:pre;" escape="false"/> It will works for you. Thanks for the update @VigneshwaranG


4

You need to set your white-space style to pre-wrap. Take a look at the CSS white-space Property: normal Sequences of whitespace will collapse into a single whitespace. Text will wrap when necessary. This is default nowrap Sequences of whitespace will collapse into a single whitespace. Text will never wrap to the next line. The text continues on ...


4

The Id of an apex:inputTextArea is modified by the runtime system that guarantees it will be unique on the page. As a side effect, this means you can't generally use those Id values without some extra effort, such as using $Component. Fortunately, CKEditor.replace supports using an element instead, so this should probably work: function ReloadCKEditor() { ...


3

If your text field is referenced anywhere in Apex code, you won't be able to change the data type until all references are removed. See this answer for more information on exactly what is involved in doing this. Other than that (admittedly considerable) issue, there should not be any problems changing from a text field to a long text area. You should not ...


3

The long text area required attribute is missing while creating the field but you can set the field as required from the page layout by clicking on the wrench icon and checking the required attribute.


3

Update: A KEY factor in handling various languages and character maps in ExactTarget landing pages is to be certain that in the pages "Properties" settings you select "Unicode UTF-8" as the character set. If this is not set the system will only render whatever characters are included in the selected set (ie. "United States - US-Ascii"). Applying this setting ...


3

Due to ease of use and implementation, I would suggest using TinyMCE as an editor for landing pages in ExactTarget. You can upload the js file to ExactTarget's portfolio, and call it on your page like this: <!-- Place inside the <head> of your HTML --> <script type="text/javascript" src="<your installation path>/tinymce/tinymce.min.js"&...


3

Are you adding them via .csv? If the encoding of the file that is storing the information is Unicode (or whatever encoding is needed) the Data Extension should accept it correctly since you said they are set to a field type of 'text.'


3

Generally users don't put that much in the notes but when they do it messes the rows up because the words get wrapped and it makes the row extremely long just for that one field. Is there a way to limit it from showing the word wrapping at all or just a few lines of the word wrapping What you're asking about is called "table text clipping". The answer is "...


3

Write a validation rule to prevent any/all special characters you want to locate and do a dummy data loader update to "touch" all records. The reject file should contain all the records with the special characters, thanks to the validation rule.


3

Not a direct answer, but where you have detailed logic to implement it pays to move that logic to a separate class so you can also easily build test cases for it. (You then call the class from the trigger.) This also follows the idea of writing code at a single level of abstraction. So here I would create this class: public class Names { public static ...


3

Why not just emit the JSON into the page so it is immediately parsed by JavaScript: CCx.pageJobSelection.initialize( {!jobMapJSON} ); and then there is no need to parse yourself: module.initialize = function (options) { data_jobPostings = options; }; This should avoid the need for any replacing. Its also worth using JSON.serializePretty to make ...


3

I just discovered a work around for this here. Create a Formula field that uses the LEFT formula and filter on that. You cannot filter on the ENTIRE long text but you can filter on part of it: Legal_Street__c is a long text area. I created a formula field call StreetConc__c: LEFT(Legal_Street__c, 40) I then created a dummy record and put the text '...


3

First, you are loading the CKEditor script in a wrong place. You must load it at the start of your VF page. Then, the id you put on your apex:inputTextArea is not the one generated by Salesforce at the page rendered. You will have to request by using the class of the input, then by sending its id to the plugin using the jquery attr() method. Here's the ...


3

This appears to be classic Microsoft Excel behavior when confronted with UTF-8 text. Excel likes to interpret a valid UTF-8 bytestream as if it were encoded in Windows Codepage 1252 or other encodings. In UTF-8, the bullet character is three bytes, 0xE2 0x80 0xA2. In both Windows CP 1252 and ISO Latin-1, 0xE2 = 'â'. I'm not entirely clear on how the ...


2

From the documentation of the Text Area (long): Note that every time you press Enter within a long text area field, a linebreak and a return character are added to the text. These two characters count toward the 131,072 character limit. So you should somehow cut out these characters: \rand \n


2

You have to write custom visual force page to achieve this kind of functionality. Salesforce does not support to view excrete of data or visible only some selected lines. You can create a custom field and populate the n (number of lines) lines from long text field by creating trigger. Field Definition Configurations #Visible Lines: The number of lines ...


2

have you tried using BR() in your formula? Documentation


2

a more simple and best solution would be to add the css pre-wrap which conserves New lines, Spaces and tabs, Text wrapping <apex:outputtext style="white-space:pre-wrap;" value="{!donationText}" escape="false" /><br /> Please note donationText is a long text area


2

I created the below snippet and its working totally fine <apex:page standardController="account"> <script src="{!URLFOR($Resource.jQuery,'scripts/jquery-2.1.4.min.js')}"></script> <apex:form> <apex:inputfield id="rtf" onChange="updateValue();" value="{!Account.pqr__c}"/> <apex:commandButton value="...


2

Try this. Replace Test__c with your custom object api name. MetadataService.MetadataPort service = createService(); MetadataService.CustomField customField = new MetadataService.CustomField(); customField.fullName = 'Test__c.LongTextAreaField__c'; customField.label = 'Long Text Area Field'; customField.type_x = 'LongTextArea'; customField.length = ...


2

I had a client once where the spaces in an External ID mattered (i.e. A..12 B vs A.12 B were different IDs - dots are spaces) and they wanted them to be displayed in SF. I wrote a utility method to do that for a given field and remove it (replacing with real space) as well when sending back to the external system public static String preserveWhitespace(...


2

As per my comments, one possible work around is to use the SOQL query in for loop as documented in Working with Very Large SOQL Queries. E.g. for (CustomObject__c a : [Select LongText1__c, LongText2__c, LongText3__c, LongText4__c from CustomObject__c limit 200 offset 0]) { // Your code without DML statements here } I suspect it is ...


2

I think if you put this in a formula in your flow it should work for you: SUBSTITUTE( JSENCODE( {!fieldname} ) , '\r\n', '<br>') The substitute function simply replaces the new line character '\r\n' with the tag you need <br>. The JSENCODE encodes your field as save for javascript. I don't think that should be necessary, but without it the ...


2

Files are a "successor" to Attachments and bodies of Files are searchable. You can also take a look at this comparison of different options for managing content on SF platform.


1

This trigger works perfectly without any issues. I did a test with the following trigger (added debugs in the OP and omitted some fields) and a test class. Trigger: trigger ParseTrigger on Task (before insert, before update) { for (Task c: Trigger.new) { if (c.Description != null) { system.debug(c.Description); Pattern ...


Only top voted, non community-wiki answers of a minimum length are eligible