-
-
Notifications
You must be signed in to change notification settings - Fork 168
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
[17.0][FIX] maintenance_plan: Use 'active_id' instead of 'id' in action to fix error #439
Conversation
…fix error The action 'hr_equipment_request_action_from_plan' failed because 'id' was not found. Replaced 'id' with 'active_id' to ensure the correct context value is used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, tested i runboat and code review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, tested in runboat
This PR has the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and confirmed that it resolves the issue mentioned in #414 (comment)
ping @victoralmau @pedrobaeza
There is also this other PR #437 that fixes this and something similar. |
Good catch! The other PR is more complete . I tested it, and it resolves both issues. Therefore, this one can be closed, and we can proceed with the other PR. |
Merging #437, as it's more complete, and it's even older. |
The action 'hr_equipment_request_action_from_plan' failed because 'id' was not found. Replaced 'id' with 'active_id' to ensure the correct context value is used.
cc https://github.com/APSL 164938
@miquelalzanillas @lbarry-apsl @mpascuall @peluko00 @javierobcn @ppyczko please review