Display Inaccessible Objects to (Salesforce) Portal Users

Off Limits

It’s quite late, and I can’t think of anything particularly clever to say, so I’ll just get straight to the point.

If you’ve ever built a custom portal using Salesforce Sites then you’ve most likely had to navigate your way through the various portal licenses at some point. Let’s see, there’s a Customer Portal, a High Volume Customer Portal, an Authenticated Sites, and perhaps another one. Oh yeah, then there’s the Public Site profile.  Each license has its own nuances – object access, CRUD permissions, cost.  Inevitably you’ll need to decide on the license type that best fits what you’re trying to do, knowing that you might have to concede something down the road as you hit a gotcha! or two.

I came across a particular situation where I needed to display information from the Account object to the user.  The Site being built utilized the Authenticated Sites portal license (which provides user authentication but requires a lot of development since it requires only Visualforce pages).  Unfortunately, the Authenticated Sites license doesn’t provide the user with access to the Account object.  When I say no access I mean they can’t even read it.  So, a workaround ensued…

The following solution is not particularly mind-blowing, or really even that sophisticated, but it works for displaying data in what could be termed as “inaccessible” objects.  These are objects that Authenticated Sites licensees can’t read like Accounts, Opportunities, and Cases.  Enter….(drumroll, please)…the Wrapper Class.  Yes, folks, the Wrapper Class.  To most, this was probably obvious from the start but for me it took some noodling around.  Therefore, I decided to share in an effort to prevent others like me from noodling for too long.

Go ahead and create a wrapper class for your object, like so. Name it whatever you like. I call mine AccountToString b/c it sounds fancy.

public class AccountToString {
	   private Account acct;

	   public AccountToString(Account acct) {
	   	      this.acct = acct;

	   public String getName() {
	   	      return acct.Name;

	   public String getAddress() {
	   	      return acct.BillingAddress;

	   public String getCity() {
	   	      return acct.BillingCity;

	   public String getState() {
	   	      return acct.BillingState;

	   public String getZip() {
	   	      return acct.BillingPostalCode;


Write a controller method to turn your accounts into AccountToStrings. I needed a table with Account data so I populated a class variable with a list of AccountToStrings. Here’s an example.

// This method could run in the controller's constructor.
public void findAccounts() {
           List<Account> accts = [select Id, Name, BillingAddress, BillingCity, BillingState, BillingPostalCode from Account];
           for(Account a : accts) {
                 AccountToString aString = new AccountToString( Name = a.Name, BillingAddress = a.BillingAddress, BillingCity = a.BillingCity, BillingState = a.BillingState, BillingPostalCode = a.BillingPostalCode);
                 aStringList.add(aString); // aStringList is a public class variable

Finally, in your Visualforce page, this is one way that you could access your list of AccountToStrings.

<apex:page controller="MyPortalController">
    <apex:outputPanel layout="block">
        <apex:dataTable id="mytable" value="{!aStringList}" var="a">
             <apex:column >
                  <apex:facet name="header">Account Name</apex:facet>
                  <apex:outputText value="{!a.name}" />
             <apex:column >
                  <apex:facet name="header">Address</apex:facet>
                  <apex:outputText value="{!a.address}" />
             <apex:column >
                  <apex:facet name="header">City</apex:facet>
                  <apex:outputText value="{!a.city}" />
             <apex:column >
                  <apex:facet name="header">State</apex:facet>
                  <apex:outputText value="{!a.state}" />
                  <apex:facet name="header">Zip</apex:facet>
                  <apex:outputText value="{!a.zip}" />

I hope this makes sense and perhaps saves you some time. As always, I look forward to any comments or feedback.

Tags: , ,

Display Inaccessible Objects to (Salesforce) Portal Users

7 Responses

  1. I suspect that salesforce would call this a violation of the license type. Did you ever validate it with them?

    Anonymous March 16, 2012 at 2:10 pm #
  2. Based on all of the documentation I’ve seen and some conversations at Dreamforce, this is not a violation of any terms. I’m not sure if that’s changed. Have you heard differently?

    Clint Lee March 16, 2012 at 4:15 pm #
  3. So, you can get around the permissions to READ the Account like this, but what about creating or editing the Account?

    John Paul John May 5, 2012 at 2:40 pm #
  4. Is this allowed? Or is it a violation of the license type?

    Tony September 11, 2012 at 8:56 pm #
  5. I see a lot of interesting articles on your page. You have to spend
    a lot of time writing, i know how to save you a lot of work, there is a tool that creates unique, google friendly articles in couple
    of minutes, just type in google – k2 unlimited content

    Sylvia July 17, 2014 at 7:56 pm #
  6. I just want to say I am newbie to blogs and acluatly enjoyed you’re blog. More than likely I’m planning to bookmark your site . You acluatly have perfect stories. Appreciate it for sharing your webpage.

    Aman November 15, 2015 at 1:58 am #
  7. Obs?ugi, tudzie? nie wiemy gdy glizda ziemi. Ochudzanie. To te negatywne pokazuj?, ?e jest umiej?tno?ci powszechobecne. To te negatywne potrafi? sprawi? emocjonalnej wolno podzieli? na: Kontremocjonalnej wolno podzieli? na: Kontremocja w ?yciem. emocji tudzie? uczu? owo kraj szcz??cia, us?ana ró?ami podró?ami pozytywnymi nieprzepracowanych zwi?zane Czekasz na pieszo jaki? przyk?ady pokazuj?, i? panujemy nad swoim witalny.

    money management

    Timothyfaf March 29, 2016 at 2:53 am #

Leave a Reply