There is a workaround using workflows as mentioned here.
I've had trouble getting this to work in my scenario, was wondering if anyone could shed some light on this.
I have two objects:
1. Price List Item
2. Summary Output
I have a long text field on the ‘Price List Item’.
Then I have a formula on the ‘Summary Output’ that needs to pull in the long text from the ‘Price List Item’ to output to a proposal output from the summary output.
I’ve tried several configurations based on what was outlined to no avail. Could anyone clarify considering this scenario?

  • so I assume you want some sort of concatenation of price item texts into a field on the associated parent output object? If so , are you certain formulas are the best approach ? Would a trigger on the price item provide an easier solution?
    – max
    Feb 4, 2014 at 18:16
  • I'm not sure, no there is no concatenation on the text. We just have a need for more than the 255 char limit on the standard text area, so the only way to get the long text through a formula is with a workaround. I'm not well versed on triggers so am unsure the benefits or use in the issue. Thanks for your feedback, if a trigger can do the job I would certainly like to try.
    – Miklr
    Feb 4, 2014 at 19:12
  • How the objects are related (what has the lookup to what; I assume you have lookup from Summary Output to the price list item?)
    – eyescream
    Feb 4, 2014 at 22:32
  • Yes sir, the Summary Output is where I've been able to do a Formula text area (255) with successful look-up to the Price List Item table. So with the workaround I'm trying to get it to pull in the long text area.
    – Miklr
    Feb 5, 2014 at 17:01
  • I tried the workaround in your link and it works fine. The target field in Summary_Output can't be a formula field, it has to be a long text field. In your WF Field Update, are you using the option 'Use a formula to set the new value' and then clicking the Formula Editor? The 'insert field' button will bring up the long text field on the lookup (Price List Item). The WF workaround is copying the value from one record to another. N.B. If the price_list_item field changes (e.g. to correct typos), it won't propagate into the Summary_Output
    – cropredy
    Feb 6, 2014 at 1:59


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.