Feature Request: Add ability to select existing Salesforce Files for images in Lightning Knowledge articles
Trailblazer Community

Feature Request: Add ability to select existing Salesforce Files for images in Lightning Knowledge articles

Content and Files , Service , Knowledge , Spring 18 , Lightning

Last updated 2020-12-16 ·Reference W-4824153 ·Reported By 46 users

In Review

Summary
This Known Issue (KI) is a continuation of the previous one here:

Images added to a Rich Text Area field on a Knowledge Article created in Lightning are visible only to the creator
https://success.salesforce.com/issues_view?id=a1p3A000000mCiTQAU
Reference: W-4428041

With Spring '18 the KI above was marked as fixed and proper visibility for images in articles when uploading a file from user's local machines was corrected however, the ability or option to select an existing File from Salesforce was removed from the Knowledge Article's rich text editor's (RTE) Image tool with the release.

More details on this change have been outlined in the Article here:

Unable to select Files from Salesforce when adding images to Knowledge Articles in Lightning
https://help.salesforce.com/apex/HTViewSolution?urlname=Unable-to-select-Files-from-Salesforce-when-adding-images-to-Knowledge-Articles&language=en_US

This new work item was created to track creation of new functionality that would allow the application to set appropriate visibility for Images added to Knowledge Articles in Lightning Experience when they're selected from existing Salesforce Files.

Once the visibility for selecting an existing File from Salesforce has been addressed, the next step would be to re-introduce or add the ability or feature to select Files from Salesforce when adding an Image to Knowledge Articles in Lightning Experience.

Repro
1. Create a rich text area (RTA) field and apply it to your Knowledge page layout.

2. In Lightning Experience, create a new Article and click the Image tool in the RTA fields available rich text editor (RTE) tools.


Actual Results: Prior to Spring '18 users had the ability to select images from their local machines or existing Files from Salesforce however, appropriate visibility to the image or file was not set and only the user who added the File could see it when viewing the Article.

Now with Spring '18 users only have the ability to select Files from their local machines and doing so sets appropriate visibility so that other users can properly view the image in articles.


Expected Results: Users would have the ability to select existing Files from Salesforce or upload a new file to add as an image in in the RTE Image tool would set appropriate visibility so that everyone viewing the article would be able to properly see the image.

Workaround
None at this time.

Existing images that have been added to Articles in Lightning from Salesforce Files prior to the Spring '18 release will need to be downloaded or saved to user's local machines and then re-added or replaced using the RTE Image tool's only available option to select the file from user's local machines.

Updates
9/16/2019: This Known Issue has been converted to a Feature Request or work item that is the Salesforce internal equivalent of an Idea on the IdeaExchange. Please consider creating or promoting an Idea for this so that we may see the way this feature currently functions improved upon with a future release.

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 CS1 CS2 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS16 CS169 CS165 CS160 CS173 CS17 CS174 CS18 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS201 CS203 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS46 CS47 CS49 CS50 CS52 CS53 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS999 CS99 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU45 IND1 IND2S IND3S IND5 IND7 IND9 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA172 NA174 NA171 NA173 NA196 NA202 NA21 NA46 NA49 NA52 NA61 NA62 NA64 NA65 NA66 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.