Best practices for adding external Rich Text to Workfront Rich Text fields | Community
Skip to main content
B
BretKr
March 4, 2021
Question

Best practices for adding external Rich Text to Workfront Rich Text fields

  • March 4, 2021
  • 7 replies
  • 2928 views

Does anyone have a best practice solution for bringing text into a Workfront Rich Text field. We are finding when moving text from Rich Text fields in other applications that we are running into characters that are not accepted such as trademark and bullet symbols and we are losing things like URL links and highlighting. Salesforce is one of the source applications where this has been a recurring problem. Is there a parser that can take Rich Text in various formats and bring it easily into the JSON required by the Workfront Rich Text field?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    7 replies

    C
    CiaranCa
    Level 4
    March 5, 2021

    Hi Bret, what modules are you using to move the text over to Workfront? I don't think there should be an issue if its Create or Update Record, but if it was a custom API call you might run into issues unless you first use the "Create JSON" module to place the text into and then send that JSON as the body of your API query.

    B
    BretKrAuthor
    March 5, 2021

    I have a very simple scenario...

    1. Read a Salesforce opportunity and capture a Rich Text field
    2. Update a Rich Text field in Workfront with the SF value

    Using Update Record like you would for a normal field does not work because it is expecting a JSON payload.

    I tried using a Custom API call and that at least got basic text from SF into the WF field, but it is erroring out on a variety of characters such as trademark and bullets.

    I didn't think there should be an issue either, but apparently you cannot treat WF Rich Text fields like other fields.

    CrisDonaldson
    CrisDonaldson
    Level 3
    August 31, 2022

    Hello, could you share the custom API call you used for this?

    C
    CiaranCa
    Level 4
    March 5, 2021

    Ah you are updating a "text field with formatting" in WF, I missed that part, we haven't started using those fields but i'm guessing its similar issues to the typeahead field issue I ran into last year in Fusion, they cannot be updated in the same way as a simple text field.

    If its working when there is no special characters but failing when there is, they probably just need to be escaped. Are you using the "Create JSON" module before sending it via the custom API card, have you an example of a query body you sent to WF that failed?

    M
    MichelleMc6
    Level 3
    February 23, 2023

    Hi @bretkr - I saw this post and I'm trying to do the exact same thing. Push text from a Salesforce field into a Workfront Rich text field via Fusion. Were you able to get this to work and would you be willing to share how you did it? Please let me know. I appreciate any help you can provide.

     

    Thanks! 

    Michelle

    T
    Travis_Young1
    Level 2
    October 3, 2023

    I have been running into a similar issue I think. When I try update a rich text field using the update record module, even just typing into the field, it send an error message "[403] The following parameter value is invalid '<field name>' please adjust and try again.

    undu82
    undu82
    Level 2
    October 3, 2023

    The most important part for that update is to have the correct JSON


    This is the format:

    { "blocks": [ { "key": "", "text": "Some Text", "type": "unstyled", "depth": 0, "inlineStyleRanges": [], "entityRanges": [], "data": {} } ], "entityMap": {} }

    Just add the desire text under text and you are good to go.

      T
      Travis_Young1
      Level 2
      October 3, 2023

      Perfect, thank you so much!

      A
      Adobe Employee
      AkshayYaAdobe Employee
      Adobe Employee
      February 14, 2024

      Hello ,
      I am running into trouble when my hyperlinks have a space which I replace by %20..
      I need to escape the % character 
      This throws invalid parameter error from the attask api,this is a custom rich text field.

      Terms & ConditionsAccessibility statement

      Loading footer...