Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mismatched activities in Account view #376

Open
biostaz opened this issue Jun 5, 2023 · 2 comments
Open

Mismatched activities in Account view #376

biostaz opened this issue Jun 5, 2023 · 2 comments

Comments

@biostaz
Copy link

biostaz commented Jun 5, 2023

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
image
Inheritance scheme incorrectly generates join on Customer ID and Order ID

Expected Result
image
Generated query correctly resolves relations between Order, Customer and Account.

Proposed Solution
image
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

  • OroCRM version: 5.1.*
  • PHP version: 8.2
  • Database: PostgreSQL
@damlox
Copy link

damlox commented Jul 5, 2023

is anyone here?

@anyt
Copy link
Contributor

anyt commented Jul 5, 2023

Hi @damlox,
The team confirmed the behavior described above, and we are clarifying whether it is a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants