Expand the External Lookup Fields to Support Rich Text Functionality

[#1]

Description - Rich text fields have a few oddities when they are used in an External Lookup Field interaction. Rich text fields can cause External lookup fields to fail to be able to be selected OR result in an output that is not user-friendly. 

Why is this feature important to you - The more consistent a feature is in Workfront, the more likely it is that I can use it to design a useful and impactful UX for my team.

How would you like the feature to work - Either bring in full support for user-friendly Rich Text results in External lookup fields, or give additional features in the setup of an External Lookup Field to allow for system admins to control the results of the field.

Current Behaviour - 

1. The 2,000 character limit on an external lookup field will run into a conflict pretty easily when returning the results of a rich text field which to my understanding has a 15,000 character limit. The results of a rich text field are returned with their JSON wrapper intact. This uses quite a few characters, especially in results with multiple paragraphs or a good deal of "rich text" like attributes. It also displays the JSON wrapped output to a user which can be extremely confusing. Additionally, a calculated field, or a block of textmode akin must be used to "Clean up" the result.

Example here:
valueexpression=IF(CONTAINS("text",{DE:YOUR CUSTOM FIELD}), LEFT(SUBSTR({DE:YOUR CUSTOM FIELD},SUM(SEARCH("text",{DE:YOUR CUSTOM FIELD},1),7),LEN({DE:YOUR CUSTOM FIELD})), SUM(SEARCH("type",SUBSTR({DE:YOUR CUSTOM FIELD},SUM(SEARCH("text",{DE:YOUR CUSTOM FIELD},1),7),LEN({DE:YOUR CUSTOM FIELD})),1),-3)),"")

2. Manipulating a field with a dependency can cause an error result on an otherwise valid choice, creating hidden "invalid" choice amongst valid choices all driven by character limits. This is difficult to control because the JSON wrapper is variable as well, so text block of 1,800 characters could be valid in some cases and invalid in others solely based on how many paragraphs were used in the text.

3. There seems to be no support for a JSON Path-based "cleaning" of the output of an external lookup field.

Example:
$.data[*].parameterValues['DE:YOUR CUSTOM FIELD']     ---> This one works, but results in the JSON wrapped text
$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'].blocks[*].text     ---> Does not work
$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'].blocks[0].text    ----> Does not work

If either of the 2nd or 3rd approaches worked, we could bypass some of the obscure and inconsistent outputs we get as of today by trimming the results of their JSON wrappers.