Summary
Current activity inheritance generated by OroCustomerAccountBridgeBundleInstaller assumes incorrect relations between Account and Order, resulting in mismatched activities being shown in Account's view Activity List. This is related directly to the way Activity List view retrieves Activities via defined inheritance scheme.
API is not affected by this issue and responds with correct activities associated with any given Account.
Steps to reproduce
Navigate to the View of any Account.
Inspect query generated to retrieve associated activities.
No additional steps required. Clean installation of current 5.1 version generates faulty relation definitions.
Actual Result
Inheritance scheme incorrectly generates join on Customer ID and Order ID
Expected Result
Generated query correctly resolves relations between Order, Customer and Account.
Proposed Solution
Defining Order's path of relations with the inclusion of customer entity resolves the issue.
However I strongly suspect that this cannot be treated as a final solution, and proper migration would be required to generate correct relations schema for existing activities.
Summary
Current activity inheritance generated by OroCustomerAccountBridgeBundleInstaller assumes incorrect relations between Account and Order, resulting in mismatched activities being shown in Account's view Activity List. This is related directly to the way Activity List view retrieves Activities via defined inheritance scheme.
API is not affected by this issue and responds with correct activities associated with any given Account.
Steps to reproduce
Navigate to the View of any Account.
Inspect query generated to retrieve associated activities.
No additional steps required. Clean installation of current 5.1 version generates faulty relation definitions.
Actual Result Inheritance scheme incorrectly generates join on Customer ID and Order ID
Expected Result
Generated query correctly resolves relations between Order, Customer and Account.
Proposed Solution
Defining Order's path of relations with the inclusion of customer entity resolves the issue.
However I strongly suspect that this cannot be treated as a final solution, and proper migration would be required to generate correct relations schema for existing activities.
Details about your environment