RAP contract violation in Unmanaged Scenario

[Dinesh_CDK]

Below is the ATC check error from the behavior definition of unmanaged scenario. This error was not coming before the latest release.

Behavior Definition has one function import. No CRUD operation involved.

Any pointers on how to resolve this issue.

Multiple markers at this line:

- RAP Contract Violation for RESULT: READ with a duplicate existing key: Tests validating RAP BO contracts

- RAP Contract Violation for RESULT: READ with an existing key: Tests validating RAP BO contracts

- RAP Contract Violation for FAILED: READ with an empty key: Tests validating RAP BO contracts

- RAP Contract Violation: Check could not be executed due to duplicate keys: Tests validating RAP BO contracts

[volkerdrees]

Hello,

according to the ATC it seems that you are not providing the RESULT as defined in the Behavior Definition. You've probably defined "result [1] $self" in the BDEF. This means a consumer expects to receive an instance of the same type as the result per provided key.

Best Regards, Volker