Hot answers tagged

8

From the Order documentation (my emphasis): Represents an order associated with a contract or an account. So I'd say the parent is either the Contract or the Account, depending on how the Order is setup. The docs also say that AccountID is a required field and that the ContractId isn't. The more standard docs have: Contract Name Title for the ...


8

High-volume customer portal users are unable to participate in the salesforce sharing model. This means: The setting in Setup | Security Controls | Sharing have no impact on them. The role hierarchy has no impact. Apex managed sharing rules, and manual sharing have no impact. What you get instead is the ability to restrict them to seeing record where ...


8

I know this is an old question, but either the answer has changed or the answer was wrong. OWD is deployed as part of the metadata of the object. https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/customobject.htm


6

I would hazard a guess that you have sharing rules on the account that are causing the contacts to be shared. However, you can definitely determine why by going to a "deleted" contact, and clicking on the Sharing button. From this page, click on the Expand List button, and choose the "Why?" Link next to a user that shouldn't have access. It will list all the ...


5

Contacts without Accounts are called "private contacts". Contacts have a special hybrid relationship with the Account(has characteristics of both lookup and master-detail relationships)l . To answer your question, sharing rules do not apply to "private contacts". The sharing will be "private" irrespective of the sharing rules defined on the contact. Also ...


5

My tuppence worth, very much late to the party. We had a need to do this as well. Our customers needed to expose wide sets of data to their users and let them select the sub-set they wanted to process. Thus we couldn't use Sharing Rules to define the scope and needed to provide some form of synchronization/guaranteed single threading in order to check for ...


5

It looks like the answer is "no." Based on the components available listing, you can deploy sharing rules for individual objects but not the OWDs.


5

There is a small article on Salesforce help You have access to the Sharing button when your sharing model is either Private or Public Read Only for a type of record or related record. For example, the Sharing button may appear on an account even though your organization-wide default for accounts is Public Read/Write, if your organization-wide default for ...


5

Update See Known Issue: sharingModel does not update through Metadata API CRUD-based calls (W-4865521 ) Summary sharingModel does not update through Metadata API CRUD-based calls API call finishes with success = true but the sharingModel for the object is not updated One workaround that has so far come out of support case 18656360 is that you ...


5

Yes. Each object has two fields, "sharingModel" and "externalSharingModel". You can import and export these values between orgs. You'll find this setting in the CustomObject metadata. I personally use this method to set up the sharing model for standard and custom objects. There's some weird bugs around it sometimes, so some manual setup may still yet be ...


4

To answer this question you will need to answer yourself three questions 1)Have you set up a Role Hirerachy and whats the role of Sales Rep in the role hierarchy ?If your reps are higher than some of roles then even keeping it private will allow access as for standard profiles Grant Access Using Hirerachy Checkbox is always checked and you cant modify ...


4

What you expect to see depends upon what you have set for the OWD. Organization Wide Defaults apply to your entire org by default. When defined as: Public Read ONLY - Anybody(All users having access to that particular object) in your org. can read the records of the object. Public Read Write - Anybody(All users having access to that particular object) in ...


4

When Grant Access using Hierarchy is checked for custom object(For standard objects this is always checked) even if the record is private ,users higher in the role than the owner of the record still gets access to the records . A simple example can be assume opportunity is private OWD and you are Sales Rep owning an opportunity record ,you have your manager ...


4

The whole purpose of the sharing model is to ensure the correct users access the right records at the right time. This is an expansive subject and understanding this well is one of the critical pieces to getting the most out of the platform. Not understanding it, you risk reinventing the wheel programmatically, and inevitably causing yourself and others ...


4

After much research time and some headaches... I've found a solution: You can obtain the Organization Wide Default Settings of a Custom Object by using the Metadata API (http://www.salesforce.com/us/developer/docs/api_meta/). It is a Soap Web Service which is provided by Salesforce and you can use it to get many of the configurations that you have set up for ...


4

After some googling: it seems like Salesforce is transferring these videos to something called vidyard. For example, the Overview video is now located on http://salesforce.vidyard.com/watch/kXk6BaNlWJP27UyFO8vNUg, but without links to the other videos. It seems that the videos must now be accessed via help, I found another one in Setting Your Organization-...


4

No. Sharing rules open up access to records. If the user's profile does not have edit on the contact object, he will not be able to edit the record.


4

For first point yes your assumption is correct. For second point is if in future you want to restrict this for some user and allow for some users then you need to again change the OWD to private but using sharing rule you just need to update their role do its easy to maintain. Also sharing rule will only user with Role Recruiter to see the records but the ...


4

As long as the user's profile contains the Read <Object> permission (where Object is the object you'd like to display), you can display those records in a Visualforce page. By default, with Private sharing, users can only see their own records, records of users below them, and any records shared with them. As a generic example, the following code shows ...


4

It's allowing you to delete it because it's a without sharing class, in which Apex does not enforce sharing permissions. This is correct behaviour. Also recall that object- and field-level permissions are not evaluated in Apex code unless you check them yourself. In a with sharing class, you said it is giving no rows found on SOQL. This is also correct ...


3

Correct. View all access permission give access to all records. View access permission would give access to view his own records or records of his subordinates in role hierarchy.


3

You cannot change field level security by a workflow. However, you could do something like this: Create a new record type for your object Create a new page layout (on which you show this specific field) and assign it to the record type Create a workflow rule based on your criteria + field update that changes the record type


3

Organization-Wide Defaults control the sharing of a record whereas the Profile Permissions defines what each profile can do with the shared record. So your read only user would only be able to read the records and not modify them but they would be able to read records they do not own. If they did not have read on the object then they would not be able to ...


3

I don't know about the first part of your question on how to change the OWD's. You can use the Organization object though to find out the default OWD's for the org you are in. This allows you to query for the default access for standard objects Organization myOrg = [Select Id, DefaultAccountAccess, DefaultContactAccess from Organization]; System.debug(...


3

Please find this useful link for more information. https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_bulk_sharing_understanding.htm Please find comments to your queries below: 1) When I checked via User_B he also able to see same record as of User_C. Is this because the reason that User_B is above role Hierarchy of User_C? ANS:...


3

The first master-detail relationship you create on your junction object becomes the primary relationship. This affects the following for the junction object records: Look and feel: The junction object's detail and edit pages use the color and any associated icon of the primary master object. Record ownership: The junction object records inherit the value of ...


3

The only other method for sharing custom objects that may suit your needs is Apex-Based Sharing. However, it's not perfect, because you can't create triggers on sharing tables to replicate the rules appropriately, so you'd have to run a scheduled process every once in a while to sync up the tables. In other words, users will not have real-time access to the ...


2

Check the role hierarchy and Profile setting. https://help.salesforce.com/HTViewHelpDoc?id=security_controlling_access_using_hierarchies.htm&language=en_US https://help.salesforce.com/HTViewHelpDoc?id=users_profiles_view_all_mod_all.htm&language=en_US


2

If there is no role setup for your org Grant Access Using Hierarchies does not work. Option 1: Give the manager view all and manage all access (if it is ok to expose all data to the managers). To do this go to their profile and in the object permissions provide view all and modify all next to the create read edit and delete checkbox for the object If ...


2

You can actually now get this through the Tooling API! It is on the Entity Definition table. So you can run a query like this: List<EntityDefinition> sharingModel = [Select InternalSharingModel, ExternalSharingModel FROM EntityDefinition WHERE QualifiedApiName =: objectName]; Even if the Object has an OWD of Controlled by Parent, it will make the ...


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