Hot answers tagged

5

You will manage the roles in MC. Users still need to be created in Marketing Cloud, and have roles and business units assigned. The advantage of SSO is, that they would not need to provide MC credentials when logging into MC. You can select which users in SFMC would be applicable for SSO, as you still might have cases where some users (e.g. if you are ...


3

Each SObject has a sharing object (for example Account has AccountShare). You can fetch these with the condition ParentID = :accId. Further details here


2

Based on your description, it appears that the "missing" Contact is not associated with an Account. Contacts without Accounts are treated as private: A contact that isn’t linked to an account is always private, regardless of your organization’s sharing model. Only the owner of the contact and administrators can view it. Sharing rules and workflow rules ...


2

You can accomplish this using Apex Sharing or try Sharing Rules. With Sharing rules you can set the level of access to Read Only or Read/Write Basically all you need to do is to create a Sharing Rule for the object you need to modified with this logic. On the Sharing Rule creation process enter the field and the criteria. After that give the access level to ...


2

Before doing the two things below, I'd really confirm that they're experiencing different layouts at the same time after a refresh/hard refresh. They can do this in chrome by clicking on F12 and right clicking on the refresh icon and selecting "empty cache and hard reload". Note: this will erase any pinned list views they have saved. It's possible they're ...


2

Since your requirements so closely align with how role hierarchies work they would seem like the natural fit. All your work will be in defining the continents, countries, cities etc... One way or another you are going to need that data to drive the model. You might as well use what Salesforce already provides to enforce it. However, the default limit for ...


1

If someone of role a1 creates a lead then he/she can still edit the record of that lead.


1

Sharing is always cumulative, so you cannot reduce access to a record via a sharing rule. The owner of the record will still have Ownership permission (Full Access).


1

Data category visibility information is stored in the profile and permission set. Visibility information can only be retrieved using Profile(Permission set does not support category visibility information at the metadata level). Also, Salesforce recommends that you manually create data categories and record associations in an organization


1

I think you can do this by adding an Action on the opportunity page layout.. "Subsidy Opportunities". Using LWC in combination with an aura component you can build an Action. This will give you a lot flexibility in terms of visibility and access. If you don't have a Constant class you can create one as a kind of helper utility and add the profiles to that ...


1

The schema you are dealing with is: Contact -> AccountContactRelation -< AccountId where AccountContactRelation has a field Role or Contact -> AccountContactRole -< Account where AccountContactRole has a field Roles (multi-picklist) Since you are trying to display a list of Contacts and their roles on a single line of VF , you are gong to ...


1

Internal and external Roles will affect the org in the same way. Roles are Roles whether they're internal or external. Regardless of where they're used, the more you use, the slower things will get. I would not make the assumption that 510k is the max, but instead would conclude the max is 500k. Remember you need to provide a Business Use case ...


1

You can use authorization as 'Authorization: Bearer <your_session_id>'. You can get session id using UserInfo class httpReq.setHeader('Authorization', 'Bearer ' + UserInfo.getSessionId()); added based on comments As you said SOQL through REST: HttpRequest req = new HttpRequest(); req.setEndpoint('https://ap2.salesforce.com/services/data/v35.0/query/...


1

When a role is created in the Org, a corresponding group related to the role is automatically created. You don't have to create it again in your test class. You can just query it as below, Group grp = [SELECT Id, Name, Type FROM Group WHERE RelatedId = :role.Id AND Type = 'RoleAndSubordinates' LIMIT 1]; Hope this helps you


Only top voted, non community-wiki answers of a minimum length are eligible