Junction Object Security

CTAs know everything. And then there are moment when they don’t. Or they challenge documentation. Or just read the documentation differently. Or its different part. Or speak with someone else who read it differently.

Junction Object Security might be one of those small things, even though you probably rarely hit this question – what drives access to junction records?

Assumptions

As taken from Help, you can explain it in multiple ways.

Sharing access to a junction object record is determined by a user’s sharing access to both associated master records and the Sharing Setting option on the relationship field.

Looks like we need access to both parent records to have access to the child.

The first master-detail relationship you create on your junction object becomes the primary relationship. This affects the following for the junction object records:
….
Record ownership: The junction object records inherit the value of the Owner field from their associated primary master record. Because objects on the detail side of a relationship do not have a visible Owner field, this is only relevant if you later delete both master-detail relationships on your junction object.

….

As sharing is driven by ownership maybe only access to the primary record might be enough.

Let’s find out.

What we have

  • role hierarchy with two Child role and one Master;
  • two users, each of them assigned to one Child role;
  • one manager user, assigned as their boss;
  • one system admin;
  • two Master objects, both OWDs set to private;
  • one Junction object.

Testing

Scenario 1

User 1 creates a new master & child records.

They are not visible to User 2, they are visible to Manager.

Scenario 2

User 1 creates both master records, system admin creates a new junction record.

They are not visible to User 2, they are visible to Manager and User 1.

Scenario 3

User 1 creates one master record, Manager second one plus junction record.

The record created by Manager is not visible to User 1, junction record is not visible to User 1 as well.

Scenario 4

User 1 creates both master records and junction record, shared the primary master record one with User 2 for Read Only access.

User 2 can see the shared master record, cannot see any junction object.

Scenario 5

Continuation of Scenario 4 – the second master record is shared with User 2 as well.

User 2 can see the same junction records as User 1.

Scenario 6

User 2 tries to edit junction records. The relationship is set for Read/Write on both relations, he has only Read access to the both records.

Sharing Settings on Master-Detail relationship

User 2 is not unable to save the record, he will get an error when saving. He cannot change any relation (User 1 can if they allow re-parenting).

Scenario 7

User 2 tries to edit junction records. The relationship is set for Read/Write on both relations, he has Read/Write on primary one, Read Only on the secondary one.

User 2 is not unable to save the record, he will get an error when saving.

Scenario 8

Continuation of Scenario 7 – the MD fields has Sharing Settings changed to Read Only, User 2 tries to edit junction record.

User 2 can edit junction record if its sharing is the same or higher as in Sharing Settings.

Scenario 9

Continuation of Scenario 4 – User 2 tries to create junction record.

User 2 is unable to save the record as he will get the following error.

Error when saving record and not having proper rights on parent

Scenario 10

Continuation of Scenario 9 – primary parent record is shared with User 2 for Read/Write. User 2 creates junction record, where the second master record is not shared with User 1.

User 1 cannot see the new junction record.

Results

  • you need access to both parent records to see the child;
  • Sharing Settings on field definition can change results for savings/creating.
Napiš komentář, díky!

Farewell to Lightning Champions

When something ends something else can start … well, will see what happens now.

Three years ago I was honoured to be accepted into the very first batch of Salesforce Champions. This first batch could even choose whether they want to be Activation or App Dev Champions or both. Of course I applied to both.

First years were really good. Not just for the nice hoodie I got, but also for the semi-regular calls with product managers where we could learn more about the longer term future. Also we were a bit more involved in demos at Dreamforce or manning the booth.

Besides that it was all about creating content on our own or being guests in content prepared by Salesforce. I already forgot they hosted me at admin podcast some time ago, but this screen shot from the wrap party confirm it.

What never happened to me was the peer-to-peer part of the program, where the idea was to help end customers with getting ready for the switch.

And then came the time when everyone was on Lightning or at least it wasn’t topic anymore. So we were renamed to Platform Champions but what we did never really changed. Actually it was pretty good as suddenly even the blog posts about flows counted as activity.

Speaking about activities that was the part I started to hate about a year ago. Of course we had to report them, so the team can prepare such nice statistic as the one above, but I realised I don’t really want to do this paper work, I want to promote, speak and write as I want. Mixed together with the – logical – requirement of what is the minimum number we should create on quarterly basis to stay in the program. And the fact that I run out of idea or half of the things didn’t count under the program as they were part of my job/community leader.

Time to quit, especially as I got a feeling I’m not getting much in exchange. All that feeling even stronger due to Covid lockdown.

Farewell

And then we got the news – the Platform Champions program closed down, good job everyone. Some had hard feelings about that, some felt like they will miss something, some others (as me) didn’t really care and fully understand the decision. Keeping the momentum must be super hard.

So we had a wrap party and it was really great, especially the memories and take aways people shared. How they got a job because of their involvement. How they met new people. How they learnt new things. How they became better at presenting.

At that was the moment when I – again – realised how happy I was being part of this force. It was great experience and thank you everyone who made it happen. And who knows, maybe I’ll become part of another Champions program, as there are a few of them still running.

At least I hope – where are you Marketing, Analytics and Quip Champions?

Napiš komentář, díky!

S Eliškou Netopilovou

Můj první podcast – s Michalem Mravináčem – se vám prý moc líbil. A tak tady mám dalšího člověka ze Salesforce. Eliška Netopilová vystudovala diplomacii, k Salesforce se dostala jak slepý k houslím u zákazníka, pak přešla k partnerovi a nakonec přímo do Salesforce. A právě tenhle mix svých životních zkušeností vnímá jako velkou výhodu.

Přechod do Salesforce znamenal i zvětšení projektů, na kterých dělá. Koordinace je výrazně náročnější a současně znamená zpomalení projektu, včetně toho že je potřeba ještě víc přemýšlet o tom co člověk dělá. Hlavně nadnárodní projekty jsou náročné tím jak se problémy multiplikují a člověk musí myslet i na různé zákonné rozdíly.

Quip na projektovou dokumentaci včetně finálních dokumentů, Chatter a Slack na okamžitou komunikaci, aktuálně se vše migruje na Slack. A Slack umí kanály přesouvat do složek, což jsem vlastně dosud nezaregistroval.K tomu na projekty typicky produkty Atlassianu – Jira, Confluence, Bitbucket – na vlastní řízení projektu.

Pozice není až tak důležitá, zajímavější je vědět na kterém projektu člověk dělá. Typicky neimplementují sami, doplňují na projektech partnery a pomáhají jim získat to nejlepší ze Salesforce.

Pozice v Salesforce Professional Services jsou rozdělené na solution a technické:

  • Solution architekt – analyzuje potřeby, navrhuje řešení a současně ho implementuje; orientace na komunikaci s klientem;
  • Senior Solution architekt – komunikuje s managementem, navrhuje high level řešení, připravuje release updaty, neřeší detailní potřeby;
  • Technical architekt – APEX, integrace, nemusí nutně vyvíjet, ale musí umět kód číst;
  • Program architekt – hodně technický člověk, který umí skvěle komunikovat a má přehled i o technologiích mimo Salesforce, hodně seniorní pozice na velkých projektech;
  • Custom Success Specialista – měli by být na projektu ideálně úplně od začátku, měli by mít vazbu na management zákazníka, kam firma směřuje a současně rozumět tomu co se dodává; mají nejsilnější vazbu na produktový management interně; musí být schopni to uřídit na té politické úrovni.

Čím vyšší pozice tím víc se solution a technika prolíná.

Po vzdělávání se musí pídit malinko sami, rozdíl ve zdrojích oproti partnerům asi není až tak velký, jak by člověk čekal.

Může si člověk vybírat na kterém projektu chce dělat? Až tak moc ne, jsou kolečka v systému. Lidé se vybírají podle informací co o sobě zadají v systému. Vazby jsou důležité, lidé se vzájemně na projekty doporučují pokud spolu rádi spolupracují.

Nábor do Salesforce – doporučení věci zjednodušší, potom pohovor s recruiterem a pak začínají kolečka pohovorů, většinou jsou tří fázové – konzultační pohovor, technický pohovor a pokud projde tak je panelový pohovor se 4 – 5 lidmi, kde je i praktická case-study. Co největší množství lidí z různých pozic je právě k dosažení nestrannosti.

A tak pokud chceš do Salesforce i ty, tak pošli Elišce životopis a třeba tě doporučují, a jinak budu rád, pokud se přihlásíš k odběru a případně necháš i zpětnou vazbu. Díky!

Listen on Apple Podcasts Listen on Spotify Napiš komentář, díky!

Working From Home, Karen Mangia

Salesforce MVPs get some extra benefits and I’m glad I’m one of them. This year we could order what we want from a special collection, so not only I got a new microphone, so my podcast sounds better, I also got this new book from Karen Mangia about working from home.

New equipment

Actually what new you can learn after 18 months working from home, right? I was surprised how many notes I made while reading the book, so let’s wrap it up here.

Research shows that delays of 1,2 seconds via video will make people perceive a responder as less friendly or focused, when it’s really just their internet connection!

The truth is I’m most likely less friendly or focused, it isn’t just the connection. But jokes aside, I’m really surprised how people complain on their connection all the data even people from countries where I would expect no problems and speedy connection. I love the internal debate we have on chat, where people boost how they have 200Gbps or 500Gbps connection while they still keep their camera off because it is slow, while I’m on my mobile from day 1 and lately limited to 10Mbps and have no problem at all. Maybe except being perceived as arrogant.

But you know what I see every time I look at a piece of sheet music? A lot of white space. Without a pause, music is just a noise. The rests in music aren’t signs that the composer is being lazy – it’s the composer being smart.

This is strong point and something I miss the most. Not having transitions. It is great that I can finish a call, have a lunch with family and go back to another call, but I’m really missing the transition between office and home, between work and family. And no, walk around the house to get this feeling back is not a solution, at least for me. So should I really try to have a dance party before making a dinner?

When you invest in something new, you must divest of something else.

Back-to-back video meetings have suddenly become the new routine. … Is that always-on routine serving you? Putting you at your best?

I remember two changes in my life during Covid. The first one was how suddenly meetings stopped right at the end, not a minute longer. And how much I (still) appreciate it.

The second is one project, where people were not afraid of 15 minutes long meetings, which is awesome, because why spend an hour on something you can solve in 15 minutes. The only problem I immediately noticed was how suddenly even the smallest breaks I had on my calendar disappeared.

Now I’m trying to go to task #2, as I have no problem with rejecting meetings from #1 and #3:

  1. Does it have to be?
  2. Does it have to be me?
  3. Does it have to be me right now?

Spectacular Online Meetings

I love to read all the stories how people improved their home office to look better. Michal’s description is the last I read and really like it even though I don’t really follow the advice. At the beginning of lock-down I bought a standing table and then I got the microphone and light as seen above. No better chair, additional screen or anything other improvement, not really a space to do make something great in our 3+1 flat shared by 5 people.

But I like the idea to rethink your budget – before Covid I would be requested to go to client locations quite often and „what would I spend on that meeting“? Just put those money into your home office setup and it kind of costs you less and improve your delivery a lot.

You cannot do a three-hour working session anymore.

Be human

I must say that I hate voice messages as I need to listen to them and really focus, text is so much easier and quicker to process.

At the same time it is an interesting idea to send a client a video message with a few quick takeaways which you recorded while you walked your dog outside and even had a time to say hi to your neighbour. I mean – so unexpected, human and real, we probably don’t have to pretend we are all business all the time.

Shorten meetings, more to the point, smaller audience.

Unfinished slides which you co-create with the client. Another interesting idea, totally understand the feeling of ownership client will immediately get.

Segment, check-ins, built in breaks, during which you summarise what was agreed so far so there is less miscommunication.

This chapter was really good and full of interesting ideas, takeaways and things you need to be aware of.

Redefining Success in the New Normal

When you see the replies you can immediately feel better (hopefully). Because success is not a title, money or anything else. Success is being happy and it also doesn’t matter whether someone else validated it.

The key to more success is actually less.

Less obligation. Less commitment. Less overreacting. Less pressure. Less discouragement.

And this one is absolutely awesome and I feel I really suck at it.

Success isn’t about repetitively demonstrating that you can push harder, so that you can shove heavier rocks up higher hills. Success is demonstrating that you can get other people to join you in your charge.

Virtual events

Obviously the chapter about virtual events was really interesting to me. We did CzechDreamin, I also helped with Nonprofit Dreamin and in both case I shared the same feeling – why would people pay for it, when there are tons of another events/webinars/videos. And also what is the difference between webinar and event, what really defines it?

And then I read about events who went virtual, still charge hundreds or thousands of dollars for a ticket and their attendance went even higher.

All the platforms are cool, but they don’t make the difference.

Surprisingly no recording can be a solution as people have to focus, not hope to replay later – at the same time attendees don’t really understand why there will be no recording.

Swag box is another big thing, we all love them and when you get them before event … there is not more which can beat it. The only downside, from European perspective, is how expensive the postage can be. We thought about it for CzechDreamin and the costs were higher than the costs of the swags, so it didn’t really make sense to us. Plus all those CO2, right?

In-Person Check-In – are they serious? It looks like a ridiculous idea but I really love especially it for the more expensive events.

Be intentional about not taking every meeting on camera. Take that call while you’re walking around your blok. Get some fresh air, get away from your screen, give your eyes a rest. Give your mind a slight mental reboot. These micro adjustments can have macro impact on how you feel by the end of the day.

Get connected

Connections are everything these days and I know that I struggle with networking. Still some advices here really surprised me.

Avoid connection requests which obscure the true intention behind. Requests such as „Can I pick your brain?“ or „Could we get coffee or virtual coffee?“ Actually I love to send these requests because those are the real reasons, I don’t really plan much further. And immediately offer reciprocity? Introductions I can make, the insights I can share. To me this feels strange and bounding and not sure I would accept such request, because what they really want when they immediately list what all they can do for me?

Write a recommendation – I did it a long time ago, that was a great feeling, to write the recommendation on LinkedIn just because I wanted, not because someone asked. Need to put it on my list again. And it is also super hard I would say.

Get it and read it

Obviously you can buy the book at Amazon and enjoy it yourself. Or if you are based in Czech Republic I’m more that happy to pass it forward, just let me know. Because it is full of interesting ideas and things which will make you stop and think again.

Napiš komentář, díky!

B2B Solution Architect

Have you heard? There is a new certification and Shoby Abdi greatly summarised what you need to pass it.

This certification makes so much sense and even though you will see B2B Commerce in most questions you don’t really need to know it, I had maybe 4 questions where I could use the knowledge. Which makes it really similar to the B2C Solution Architect, where you didn’t have to know a lot about B2C Commerce features, you cared only about the integration points.

While the name suggest that it might be similar to the B2C architect, just focused on different target group, I would say those two exams are completely different. The B2C Solution Architect referred a lot to B2C Commerce, Marketing Cloud and Service Cloud and you needed more the technical knowledge, understand integration patterns and what is the use case for each system. Plus it has quite weird list of prerequisites.

B2B Solution Architect has simple prerequisites – Application Architect Certification. And I would say it is more about processes, there are questions about project management, how to correctly order the implementation in terms of which products first and which later, what needs to be done when, etc. I would say my preparation for PMP exam helped me a lot.

This credential validates that a B2B Solution Architect can provide guidance, as well as combine guidance from different enterprise architecture viewpoints to create solutions that generate strategic business value for customers, including:

Business: demonstrate business leadership by guiding companies on a multi-cloud solution journey emphasizing differentiating customer experiences

Delivery: drive successful outcomes by advocating for multi-cloud implementation considerations and best practices based on use-case delivery knowledge which spans the Salesforce Customer 360 Vision and Platform

Technical: provide technical leadership by selecting the proper multi-cloud product features that best align with a company’s vision and business value goals

Which makes it also great for those on the CTA journey. Some people might say they want to focus on the CTA exam and do this later on, I would argue to go for this even before CTA because you don’t need extra knowledge and you should be able to pass it as preparation for CTA as it is highly related.

The PLC (for partners) preparation course also has a great section about Business Process Mapping (great job Elements.Cloud), which will explain why process map like this is not sufficient.

Not good enough business process map

Do you know? Well, there is not enough details for each step, it can flow back as well, no idea who are the actors, „happy customer“ is not a process, there is no input to the first box, … In short, there are ways how to make it better so you really understand the proces down the road.

Customers have a problem with slow quoting, uses ticketing system they want to move to Salesforce and wants customers to be able to place orders via website. What will you do first?

a) put together detailed plan for all streams;
b) start with CPQ implementation;
c) implement all clouds together;
d) start with Service Cloud implementation.

A lot of interesting questions you need to think about, some are not as clear as this one. In short – if you feel you know how to manage project, set the right priorities, this is the right certification for you.

Salesforce Certified B2B Solution Architect certification
Napiš komentář, díky!