This is a new issue that appeared with the Spring 2014 Salesforce update.

We have a customer portal user.

They try to update an object that they own and they created.

Yet we see a "Data Not Available" error message.

Data Not Available The data you were trying to access could not be found. It may be due to another user deleting the data or a system error. If you know the data is not deleted but cannot access it, please look at our support page.

This seems to only affect the customer portal users Also if we remove "sharing", it works.

But we want to understand why suddenly this stopped working?

The release notes https://help.salesforce.com/help/pdfs/en/salesforce_spring14_release_notes.pdf refers to sharing sets here:

Previously, a sharing set granted access to any record that has a lookup field to an account or contact that matches the user’s account or contact. With Spring ’14, you can also determine how access is granted using an access mapping in the sharing set, which supports indirect lookups from the user and target record to the account or contact. You can determine the objects to use in the access mapping, and they must both either point to an account or contact.

But we are seeing that even the user that created the record cannot update it.

     private class Test1Class {
     static testMethod void validateTestCrash() {

        user u = [select id from user where username = '[email protected]'];
            adviser_profile__c adviser_profile = [select id from adviser_profile__c limit 1];
            system.debug('qqq adviser_profile: ' + adviser_profile); 
            try {
              update adviser_profile;
            }catch (Exception e){
               system.debug('qqq3 validateTestCrash error adviser_profile: ' + adviser_profile);
            system.debug('qqq2 validateTestCrash adviser_profile: ' + adviser_profile);

Even worse, we never see either the Exception debug line NOR the final debug line.

The code simply aborts and even the salesforce log shows nothing but a simple exit, NO MESSAGE AT ALL!!!


  • 1
    You may want to file a case on this one. That said, I've found that with portal users, because they can easily have their isActive flag set to false, its important to also check to see if they're flag is set to true. We don't tend to think of this in normal triggers/classes for SF Users, but for Portal Users, the case may be different. They don't have to "own" what they create. Their owner can also own what they create. It all depends on your security model. Lots of options available.
    – crmprogdev
    Commented Apr 28, 2014 at 22:05
  • @crmprogdev Thanks for the reply. We do have the active flag on. And we did file an ongoing case. But progress is slow and I'm hoping that stackexchange/internet can help. But the amount of information on salesforce issues and solutions online is minimal unfortunately. :( Commented Apr 29, 2014 at 1:26

1 Answer 1


See https://success.salesforce.com/issues_view?id=a1p30000000T3tKAAS

Salesforce acknowledges the critical bug.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .