[18.0][FIX] base_search_custom_field_filter: Error when define filters with related fields #1232
+10
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Hi @pedrobaeza, |
CarlosRoca13
force-pushed
the
18.0-FIX-base_search_custom_field_filter
branch
from
9f1877e to
b41ef8b
Compare
… related fields Steps to reproduce the behavior: 1. Define a custom filter with . notation like partner_id.lang 2. Access to the model defined, to check if we can use this filter. An error was thrown With this changes the field is defined in the correct point and the error is not thrown.
CarlosRoca13
force-pushed
the
18.0-FIX-base_search_custom_field_filter
branch
from
b41ef8b to
a5d1864
Compare
mariancuadranetkia
approved these changes
Jan 28, 2026
mariancuadranetkia
left a comment
mariancuadranetkia
left a comment
There was a problem hiding this comment.
I've tested in runboat and now it's working.
Member
|
@carlosdauden can you check this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Steps to reproduce the behavior:
An error was thrown
With this changes the field is defined in the correct point and the error is not thrown.
ping @pedrobaeza @carlos-lopez-tecnativa @mariancuadranetkia
cc @Tecnativa
This PR solves the Issue: #1231