Please Address the Asset Manager Caching issue
Please address the Asset Manager Caching issue.
When adding (re-adding) files of the same name the current caching configuration prevents the new image/file from getting recognized. This results in additional effort for the user and/or multiple assets with similarly names files. The most common use case is designing a tile image - making small tweaks to the image and re-adding (uploading) the file is a futile exercise due to the current, and known, caching issue.
Kevin Devine
shared this idea
While we understand the need for this feature, we have decided not to implement it, as this would negatively effect the performance of the app.
When updating an asset, we recommend to upload the image with a different name (e.g. image_v2.png, image_v3.png, etc) to avoid this issue, as documented here:
https://knowledge.exlibrisgroup.com/campusM/Product_Documentation/Managing_the_App_and_Its_Services/01_Uploading_Files#:~:text=As%20noted%20in,on%20the%20device.