SalesLeadService => CreateSalesLead Cannot Set EstimatedCloseDate Field (Doc ID 1553592.1)

Last updated on SEPTEMBER 03, 2015

Applies to:

Oracle Fusion Marketing - Version 11.1.6.0.0 and later
Oracle Fusion Marketing Cloud Service - Version 11.1.5.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.6.0.0 version, Webservice

ACTUAL BEHAVIOR
---------------
SalesLeadService => createSalesLead cannot set EstimatedCloseDate field

When SalesLeadService => createSalesLead with "EstimatedCloseDate" set to a value, it is not set in the newly created lead. However the updateSalesLead() subsequently correctly sets the value. Need a way to set it during createSalesLead() itself, otherwise two web service calls are required for one lead.

EXPECTED BEHAVIOR
-----------------------
Set EstimatedCloseDate field by the Webservice SalesLeadService => createSalesLead

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Run Webservice SalesLeadService => createSalesLead()

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users need to run two web services calls are for one lead.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms