function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Ralph YozzoRalph Yozzo 

Spring 2014 release causes "Data Not Available" when updating object as a customer portal user?

Update: This issue magically went away many days after we reported it and now we are asking to understand this fundamental bug involving the inabilility of customer portal users to "update" and "delete" data in order to avoid it in the future.  Salesforce support told us that only premier customers and partners can get a direct answer to this question and therefore we were directed to this support site in hopes of understanding these issues and avoid them in the future.

Previous post from April 28th, 2014:
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.

@isTest(SeeAllData=true)
         private class Test1Class {
         static testMethod void validateTestCrash() {
       
            user u = [select id from user where username = 'cduissue1@issue1.com.issue1'];
            system.debug(u);
            system.runas(u){
                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!!!

SALESFORCE WHAT IS GOING ON???!!!
Best Answer chosen by Ralph Yozzo
ShashForceShashForce
Hi Ralph,

This has been published as a known issue by Salesforce and it is currently in review. You can track the status and click on "This issue affects me" here: https://success.salesforce.com/issues_view?id=a1p30000000T3tKAAS

If this answers your question, please mark this as the Best Answer for this post, so that others can benefit from this post.

Thanks,
Shashank

All Answers

ShashForceShashForce
Hi Ralph,

This has been published as a known issue by Salesforce and it is currently in review. You can track the status and click on "This issue affects me" here: https://success.salesforce.com/issues_view?id=a1p30000000T3tKAAS

If this answers your question, please mark this as the Best Answer for this post, so that others can benefit from this post.

Thanks,
Shashank
This was selected as the best answer
Ralph YozzoRalph Yozzo
Hi Shashank,

Thank you for the response and the link:  https://success.salesforce.com/issues_view?id=a1p30000000T3tKAAS

It appears that the bug is still open, yet we see that all our instances are working properly again after many days of problems.

It is very surprising to me that something as fundamental as UPDATE and DELETE of objects would not be noticed by many, many customers.

We can only guess that there are NOT many customer portal customers.

Indeed, Salesforce has announced that there will be no new customer portals.

You probably cannot answer, but we'd like to know what the plan is for supporting existing customer portal applications.

Should we expect more critical bugs like this one?

Since you probably cannot answer, we believe that every person/company using customer portal should ask this question to themselves.

Thanks,
Ralph
ShashForceShashForce
Hi Ralph,

If you are not facing the issue anymore and not many customers are complaining, it means that the issue is an intermittent one, which might come back even in your case, unless it is reported as fixed by Salesforce.

Customer Portals will be supported as usual for all existing customers using them, and bug fixes too should be provided as usual, even if no new portals are being provided, owing to the move to the new "Communities". However, in the future, the support for portals may stop once they are declared as "End of Life" by Salesforce, in which case all customers need to move to "Communities". Generally, Salesforce declares well in advance when one of their features will be "End of Life", which did not happen yet for portals.

Thanks,
Shashank