• GMM
  • NEWBIE
  • 10 Points
  • Member since 2010

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 4
    Questions
  • 4
    Replies

I am encountering a strange VF error. Well, not a strange VF error (I've seen it before), but this time I can't nail down the reason why it's appearing.

 

A bit of background:

-I have a custom object created for Projects that is in a master-detail relationship with Opportunities. Opportunities is the master, Projects is the child.

-I also have a lookup on the standard Cases object to the custom Projects object. The intention of this is to associate cases with projects, in addition to the account that SFDC associates by default.

-The Projects object default view is overridden with a VisualForce page. It uses the standard controller, but there are so many fields we opted for a tabbed layout. There are a number of related lists included at the bottom of the page (Cases being one of them) using apex:relatedlist.

 

<apex:relatedList list="Cases__r" />

 

This is working fine for our internal users. Everything shows up as it is supposed to.

 

Now I am trying to get it set up in the Partner Portal. When logging in as a Partner user, and trying to browse the same project record (uses the same VisualForce page), I get an error: 'Cases__r' is not a valid child relationship name for entity Project

Of course it's a valid child relationship name, because it already works for internal users. My first thoughts were:

- Check to make sure the related list is on the standard page layout, because VF has issues with related lists if it is not included on the standard page layout. Done.

- Remove the related list from the standard page layout and add it back in. Done.

- Check the Profile permissions to make sure the user should have access to the Objects. Done. Profile has Read, Create, and Edit access to Accounts, Contacts, Opportunities, Projects, and Cases.

- Make sure the Profile has access to the VisualForce page (not that this could really be the problem, since the error is referencing something on the page). Done.

 

Where else could this be coming from?

  • February 16, 2011
  • Like
  • 0

I have two VisualForce page that use the standard controller. They are essentially identical to each other, except that one has output fields and one has input fields. Right now, I override View and Edit with the appropriate VisualForce page.

 

Is there any way to embed a VisualForce page onto a standard layout and have it be available for viewing and for editing? I tried embedding a VisualForce page onto the standard layout. It displays fine in view mode, but when I click the Edit button, I can only edit the fields on the standard layout. The VisualForce page disappears entirely. The other half of this question would be how to accomplish this given the available options of apex:outputField and apex:inputField. It seems that this does't lend a single VisualForce page to both viewing and editing.

  • December 22, 2010
  • Like
  • 0

I have created a custom object and built a VisualForce page that uses the standard controller. How can I get the related list of attachments to display? I haven't had any luck getting it to display on a VisualForce page, only on the standard page layout. Thanks!

  • September 21, 2010
  • Like
  • 0

I use the following snippet of code to display a field history for a custom object:

 

    <apex:pageBlock title="Field History">
        <apex:pageBlockTable value="{!Custom_Object__c.Histories}" var="History">
            <apex:column headerValue="Date"><apex:outputText value="{!History.CreatedDate}" /></apex:column>
            <apex:column headerValue="Field"><apex:outputText value="{!History.Field}" /></apex:column>
            <apex:column headerValue="New Value"><apex:outputText value="{!History.NewValue}" /></apex:column>
            <apex:column headerValue="Old Value"><apex:outputText value="{!History.OldValue}" /></apex:column>
<apex:column headerValue="Modified By"><apex:outputText value="{!History.CreatedById}" /></apex:column> </apex:pageBlockTable> </apex:pageBlock>

 It works just fine, but for the Field name it displays in the format: Custom_Field_Name__c and for Modified By it displays the person's SFDC ID.

 

Are either of the following possible:

1. Instead of the field's API Name, return the singular or plural label?

2. Instead of the person's SFDC ID, return the person's name?

 

Thanks! 

  • September 03, 2010
  • Like
  • 0

I am encountering a strange VF error. Well, not a strange VF error (I've seen it before), but this time I can't nail down the reason why it's appearing.

 

A bit of background:

-I have a custom object created for Projects that is in a master-detail relationship with Opportunities. Opportunities is the master, Projects is the child.

-I also have a lookup on the standard Cases object to the custom Projects object. The intention of this is to associate cases with projects, in addition to the account that SFDC associates by default.

-The Projects object default view is overridden with a VisualForce page. It uses the standard controller, but there are so many fields we opted for a tabbed layout. There are a number of related lists included at the bottom of the page (Cases being one of them) using apex:relatedlist.

 

<apex:relatedList list="Cases__r" />

 

This is working fine for our internal users. Everything shows up as it is supposed to.

 

Now I am trying to get it set up in the Partner Portal. When logging in as a Partner user, and trying to browse the same project record (uses the same VisualForce page), I get an error: 'Cases__r' is not a valid child relationship name for entity Project

Of course it's a valid child relationship name, because it already works for internal users. My first thoughts were:

- Check to make sure the related list is on the standard page layout, because VF has issues with related lists if it is not included on the standard page layout. Done.

- Remove the related list from the standard page layout and add it back in. Done.

- Check the Profile permissions to make sure the user should have access to the Objects. Done. Profile has Read, Create, and Edit access to Accounts, Contacts, Opportunities, Projects, and Cases.

- Make sure the Profile has access to the VisualForce page (not that this could really be the problem, since the error is referencing something on the page). Done.

 

Where else could this be coming from?

  • February 16, 2011
  • Like
  • 0

Hi,

 

Please help me on How to display Notes and Attachments inside Visualforce page

On a standard SFDC page, user lookup fields have a drop down to the left of the input field where you can select "Standard User", "Partner User", etc (for examples, click the "Change Owner" link for any record). The drop down corresponds to the User.UserType field.

 

I have a VisualForce page where I have a user lookup <apex:inputField />. Of course, the UserType picklist isn't displayed for me, and when I search for a user, it's restricted to only Standard users. I need to be able to search and choose a Customer Portal user.

 

UPDATE

I just noticed that one of the URL parameters in the Lookup popup when I open it from my visualforce page is "lktp=StandardUserLookup". If I change the UserType picklist on the standard page to "Customer Portal", the parameter is "lktp=CustomerSuccessLookup". "CustomerSuccess" is the internal value for Customer Portal user types.

 

How can we change that parameter??