Skip to main content
Question

Caching Issues on File Links

  • September 23, 2021
  • 0 replies
  • 41 views
Forum|alt.badge.img+14
I typically use this syntax to make a file link field (that i can pass through lookup fields)

"<a href='"& URLRoot()&"up/"&Dbid()&"/a/r"&[Record ID#] & "/e6/v0' target='_blank' >" & [Field Name] & "</a>"

This works great, but is defeated by caching issues. For example, one file field was a .doc. This document was overrwritten by a pdf file with a different name, AND the originally .doc file was deleted.

However, users that have already cached it still see AND access the word document (even though it has been deleted in QB).

Has anyone encountered this, and does anyone know a fix?

------------------------------
Michael Tamoush
------------------------------

QuickBaseJunkie
Forum|alt.badge.img+15
I can confirm I've encountered this... but don't have a solution to share :-(

The only thing that comes to mind is using the actual 'latest' version number in the URL (vs the 'current' v0).

This API run on the attachment field will return a list of versions that could be used, but it would be quite complex for something that should be easy. https://developer.quickbase.com/operation/runQuery

-Sharon


------------------------------
Quick Base Junkie
------------------------------
Terms & ConditionsAccessibility statement