The easiest way to prove it's not a cache issue is to
I ran into something like this years ago when permissions changes to the system weren't being honored by the mid-tier.
From: ARSList <firstname.lastname@example.org> on behalf of Dave Barber <email@example.com>
Sent: Monday, July 22, 2019 8:50 AM
To: ARSList <firstname.lastname@example.org>
Subject: Re: Atrium and field 112
I'm really not sure - my main knowledge of field 112 is from an in-house developed application where we lock down data. In 10 years of usage of Atrium we've never had any need for locking anything down.
The value that was in Base Element was :
;<numeric related to the "customer company">;1000000000;
I've amended the 1000000000 value to a new permissions group for a couple of CIs, and a profile that doesnt have the new permissions group or any form of Admin rights (other than Asset Viewer) can still find the CI in searches.
Have had issues with mid tier caching, but never experienced issues related to caching and permissions - guidance welcome!
On Mon, 22 Jul 2019 at 13:33, Phil Murnane <email@example.com> wrote: