[SalesForce] DML Exception while inserting share records

I am facing trouble while inserting 1 share record. When I am loggin to Admin Profile, it is working fine without any DML exception, but when I am login to Sales profile, then I am facing such exception.

I checked with DescriveSObject isCreatable() method, I can see that Sales profile has create access on Package_Share__c object.

This is the list I am inserting:

packageShareInsertList : (Package__Share:{UserOrGroupId=00540000000zHI5AAM, ParentId=a1I560000004iRIEAY, RowCause=PKG_Sales_Team__c, AccessLevel=Edit})

This is th DML Exception I am facing:

04:21:17.791 (3215279840)|FATAL_ERROR|System.AssertException:
Assertion Failed: System.DmlException: Insert failed. First exception
on row 0; first error: INVALID_FIELD_FOR_INSERT_UPDATE, invalid row
cause: []:

But Row cause has valid value that I am sure. If it was a wrong value, then other profiles would have thrown the same issue.

Please advise.

Best Answer

I believe you are having the issues because the user you are trying does not have "Modify all data" permission.

According to the documentation LINK

Apex managed sharing enables developers to pro-grammatically manipulate sharing to support their application’s behavior through Apex or the SOAP API. This type of sharing is similar to Force.com managed sharing. Only users with “Modify All Data” permission can add or change Apex managed sharing on a record. Apex managed sharing is maintained across record owner changes.

I came across another answer where this was successfully achieved via changing class's sharing model as "without sharing". Please try doing that as well.

Link to the Answer

EDIT

I believe you received error using with sharing because a user requires at-least read access to the record for which the share is to be created. LINK

If a trigger changes the owner of a record, the running user must have read access to the new owner’s user record if the trigger is started through the following:

Related Solutions

[SalesForce] INVALID_FIELD_FOR_INSERT_UPDATE, Account: bad field names on insert/update call: LastName, FirstName: [LastName, FirstName]ge

You're using the wrong record type. I verified that if you were using the correct record type, you would not receive this error. The following code works in my developer org in execute anonymous:

Id rtId = [SELECT Id FROM RecordType WHERE IsPersonType = TRUE AND SObjectType='Account' LIMIT 1].Id;
Account a = new Account(RecordTypeId=rtId);
a.FirstName = 'Test';
a.LastName = 'Test';
insert a;

While the following code produced the exact error you got:

Id rtId = [SELECT Id FROM RecordType WHERE IsPersonType = FALSE AND SObjectType='Account' LIMIT 1].Id;
Account a = new Account(RecordTypeId=rtId);
a.FirstName = 'Test';
a.LastName = 'Test';
insert a;

Double-check to make sure that you are using a record type that is valid for your profile, and has IsPersonType set to true.

[SalesForce] DML Merge Fails INVALID_FIELD_FOR_INSERT_UPDATE

I'm not sure why, but the merge statement appears to be sensitive to the fields that are in memory for an sObject when passed to the merge statement. The operation fails if any of the fields are not updateable for the current user (e.g. audit fields, formula fields, field level security settings).

The above code is running into issues since the .newSObject(null, true) method populates default values for a lot of fields that must not be visible to the standard user in your test method. For the purposes of the test method you can just create a clone with just the id to perform the merge.

merge (new Lead(Id = testLead1.Id)) (new Lead(Id = testLead2.Id));

I haven't tested how the field values in memory affect the resulting merge, so you'll want to do some testing before adjusting for merge statements you're doing.

Best Answer

Related Solutions

[SalesForce] INVALID_FIELD_FOR_INSERT_UPDATE, Account: bad field names on insert/update call: LastName, FirstName: [LastName, FirstName]ge

[SalesForce] DML Merge Fails INVALID_FIELD_FOR_INSERT_UPDATE

Related Topic