• dhong
  • NEWBIE
  • 0 Points
  • Member since 2008

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 3
    Replies
I need help updating my shipping on an oppty.  This is a formula field that uses the close date to determine the shipping cost.
Example:
  Overnight shipping is either $40, $45 or $50 depending on the close date.
 
Currently, I am using the following formula, but I now need to increase effective today (adding a third option):
 
IF (
CloseDate < DateValue("2008-08-20"),
IF (
Overnight__c, 40, IF(Overnight_Sat_Delivery__c, 45, IF(X2_Day__c, 25, IF( X3_Day__c, 23, IF( Ground__c, 15, IF(Canada__c, 60, IF(International__c, 75, IF(P_O_Box__c, 25, 0)))))))),
If (
Overnight__c, 45, IF(Overnight_Sat_Delivery__c, 50, IF(X2_Day__c, 30, IF( X3_Day__c, 28, IF( Ground__c, 20, IF(Canada__c, 65, IF(International__c, 80, IF(P_O_Box__c, 30, 0))))))))
)
 
Thank you for your help
I have to implement custom WebToLead landing page.

Standard SalesForce page submits lead form data over WevToLead servlet where the information is being stored in the database.
At the same time SalesForce populates Lead Source Details record with Campaign name, Ad Group, Keyword, Keyword phrase etc in case of Google ad lead source, or Referring Url, search engine and keyword phrase in case of organic lead source.

There is no problem to insert/update new lead information using API.

The problem is to to retrieve Lead Source Details information.

Is there any way to get Lead Source Details information using API?

Thanks,

-igor
  • July 03, 2008
  • Like
  • 0
Does anyone know of a way to reconect an opportunity so that SF recognizes it as an AdWords originated deal? I've tried changing lead source to 'Google Adwords" but there must be something more... the Google AdWords Dashboard reports still don't recognize it as sourcing from AdWords. I think the opportunity record was not created from the adwords originating lead, rather some other round about way, and I want to see it corrected in reports.
  • December 12, 2007
  • Like
  • 0