I am logging this on behalf of a customer.
Request is to improve how the cache behaves with equipment links. Currently, a link from a piece of equipment in Field is tied to the active project. Field caches the active project so if a user logs into a different project but then tries to open the link in another tab while the incorrect project is open they receive a 500 error message. The user would like to be able to open equipment links from other projects while another unrelated project is open.
This appears to be an issue with the active cache and how Field interprets it. See steps:
1. If project that the link points to is open = link opens in new tab
2. If project is different than link - link produces 500 error in new tab.
3. If source project tab is closed first - then access link, link works.
4. If another project tab is opened first then closed - link fails again.
When it fails - we get:
d8a59fb7-ad9a-49bb-bbad-3d4a8d3cfdc2:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Can there be a way to improve the experience for the user by altering the way the cache is accessed perhaps?
