Known Issues in the Oracle Policy Automation Connector for Oracle CRM On Demand

Support for stateless Web Service calls

Limitations of Custom Objects in Web Services v1.0

Limitation for Parent Object Insert mapping

Limitation for Many-to-Many relationships

Support for stateless Web Service calls

Currently in Oracle Policy Automation Connector for Oracle CRM On Demand, we are only supporting Stateless web service calls via a fixed credential for request authentication. All of the SOAP requests sent to CRM On Demand are using the stateless format which should comply with the following conditions as stated in the Oracle Web Services On Demand guide:

Limitations of Custom Objects in Web Services v1.0

There are a couple limitations with the usage of Custom Objects in Web Services v1.0:

In essence, Custom Objects (1-3) in Web Services v1.0 are only usable when it is the top-level object. In this case, all fields are present on the schema or WSDL.

See also:

Support for Oracle CRM On Demand Web Services API

Limitation for Parent Object Insert mapping

Current limitation

On the import wizard’s Select and Configure CRM On Demand objects screen, only global is allowed in the Insert entity mapping if the following conditions are true:

 

If crmodnew<object> is otherwise selected in this scenario, a validation message will be displayed and the user won’t be allowed to proceed to the next screen.

How does this affect the behavior of the connector?

This means that, as of this release, a user won’t be able to simultaneously Save and Insert (using the crmodnew<parent-object> entity) a Parent object instance.

This has been done in order to prevent users from running into Insert or Save problems brought about by mapping both global and crmodnew<parent-object> entities to the parent object. This is a result of the connector becoming confused as to which parent instance should be attached to child object instances during saving or inserting.

Limitation for Many-to-Many relationships

Currently in Oracle Policy Automation Connector for Oracle CRM On Demand, we are only supporting One-to-Many relationships between Parent and Child objects. But some object associations have Many-to-Many relationships with each other. When these object associations are used by the Connector, it may produce undesirable results; see the topic Limitation for Many-to-Many relationships.