With around 20 years on the job, Matt is one of the most experienced software developers at Pretius. He likes meeting new people, traveling to conferences, and working on different projects.
He’s also a big sports fan (regularly watches Leeds United, Formula 1, and boxing), and not just as a spectator – he often starts his days on a mountain bike, to tune his mind.
Nothing here yet.
I guess your View works out the hierarchical results based on the app and user. That sounds like you have a decent approach there David 👍 I've seen similar approaches like this on other APEX apps. Wow APEX 4, I do remember those two-level tabs. I was quite amazed how ridiculously well the approach in my blog works, I'm glad it helps. If you want to discuss further or need any help with your app, just drop me an email. My contact details on on my About Page https://mattmulvaney.hashnode.dev/about
Hey Neil. Thanks for your nice comments. Using apex_session.set_tenant_id is the standard, built-in, method of setting a tenant in APEX , is it not? Unfortunately this procedure does require an APEX session first (See my evidence below - and I also point out that this requirement isn't stated in the documentation). Therefore yes, using this standard approach adds an overhead to REST because of the requirement to establish a session first (i.e REST must set the context in the same consistent way as APEX does - i.e using apex_session.set_tenant_id). A custom context would be quicker for sure. I'll update the blog with a note, however I didn't want this blog to deviate from something is effectively the standard approach for VPD/SaaS for APEX. Is there possibility to remove this requirement (i.e to establish a session first) from apex_session.set_tenant_id a future release of APEX?
