• ed_hilpert
  • NEWBIE
  • 0 Points
  • Member since 2011

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

we are building out our Serice Cloud implementation, and need to create a custom object while viewing a case.

we created a button on the case, which uses URLFor to open the 'new' page of our custom object.  this works fine..  the page appears and the cancel button returns back to the case.

 

now we want to pre-populate some of the cusotm object fields.

 

so we reviewed the new page filed labels, and used them as the parameters.  and the data appears in the new() object form as expected, except for one.

 

on the object is an Account Lookup field.

 

in the URLFor() we pass CF00NQ0000000ld3l = Case.Accountid as the parameter.  the 18 char account ID string appears in the new() form, but we had expected it would show the 'account Name' instead of the ID field. it reports an error (not found).. if we export the accounts, this IS the id of the account object referenced in the case object.  we cannot manually 'search' using the ID successfuly either.

 

Using the Object field names doesn't work either. 

 

so, what did we miss?

 

we've spent about 12 person hours trying to debug this.. to no avail.

URLFOR($Action.Newobj__c.New,null,[
CF00NQ0000000ld3l_lkid=Case.Account],false);

 

 

sam