You need to sign in to do that
Don't have an account?
Bryan Leaman 6
File tagging in lightning
I have a need to provide a way for people to select which uploaded/related files fulfill a specific purpose (essentially, which file s provide proof of authorization). I was hoping to use the TagCsv field and when they select the file, update the tags to indicate which file(s) provide that authorization.
However, it appears that the TagCsv field is not available for files shared to an object record -- only files in a public library. It also appears that tagging is not supported in lightning.
Are there any recommended ways to implement something similar or some way to permit access to the TagCsv field on a contentversion uploaded to (shared with) a record?
My thoughts so far have been:
* Use the description field instead and add my tag at the beginning or end of it.
* Create a join object that implements tagging (RecordId, DocumentId, Tags (long text area)
* Embed a list of Ids in a custom field on the record of all the files selected for this purpose (yuck!)
However, it appears that the TagCsv field is not available for files shared to an object record -- only files in a public library. It also appears that tagging is not supported in lightning.
Are there any recommended ways to implement something similar or some way to permit access to the TagCsv field on a contentversion uploaded to (shared with) a record?
My thoughts so far have been:
* Use the description field instead and add my tag at the beginning or end of it.
* Create a join object that implements tagging (RecordId, DocumentId, Tags (long text area)
* Embed a list of Ids in a custom field on the record of all the files selected for this purpose (yuck!)
When a user uploads or relates a file, include an option for them to tag the file with a specific purpose, such as "Proof of Authorization."
When the user selects the "Proof of Authorization" tag for a file, update the TagCsv field to include that tag for that file. This will allow you to easily search for and filter files that are tagged with "Proof of Authorization" in the future.
You could also consider creating a separate field specifically for indicating which files provide proof of authorization. For example, you could include a checkbox or dropdown list that allows the user to select which files fulfill this purpose, and then update a separate field with this information. This could make it even easier to identify which files provide proof of authorization.
It's important to provide clear instructions and guidance for users on how to use the tagging system and any other fields related to proof of authorization. This will help to ensure that users are selecting the correct files and tagging them appropriately.
Overall, using the TagCsv field and other related fields can be an effective way to manage and organize uploaded and related files. By providing clear guidance and making it easy for users to select which files fulfill a specific purpose, you can improve the user experience and make it easier to manage and track files. Regards: keybolab.com
STREAMS
Salesforce Solution Provider (https://www.streamssolutions.com/partnership/salesforce/" target="_blank)