Skip to content

Conversation

@CarlosRoca13
Copy link
Contributor

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.

ping @pedrobaeza @carlos-lopez-tecnativa @mariancuadranetkia

cc @Tecnativa

This PR solves the Issue: #1231

@OCA-git-bot
Copy link
Contributor

Hi @pedrobaeza,
some modules you are maintaining are being modified, check this out!

@CarlosRoca13 CarlosRoca13 force-pushed the 18.0-FIX-base_search_custom_field_filter branch 2 times, most recently from b41ef8b to a5d1864 Compare January 28, 2026 11:08
Copy link

@mariancuadranetkia mariancuadranetkia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested in runboat and now it's working.

@pedrobaeza pedrobaeza added this to the 18.0 milestone Jan 28, 2026
@pedrobaeza
Copy link
Member

@carlosdauden can you check this?

Copy link

@sergioM-S73 sergioM-S73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional review 👍🏻
I added this commit in my migration to v19: #1238

@mariancuadranetkia
Copy link

@pedrobaeza
I'm not sure if the errors detected in the test are only from translations. Is there any way we can help resolve this?

… 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 CarlosRoca13 force-pushed the 18.0-FIX-base_search_custom_field_filter branch from a5d1864 to 4f6e018 Compare February 10, 2026 10:53
@CarlosRoca13
Copy link
Contributor Author

Let's see if doing a rebase the problem is solved

@pedrobaeza
Copy link
Member

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 18.0-ocabot-merge-pr-1232-by-pedrobaeza-bump-patch, awaiting test results.

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@OCA-git-bot OCA-git-bot merged commit 6308fa8 into OCA:18.0 Feb 10, 2026
7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 958f321. Thanks a lot for contributing to OCA. ❤️

@pedrobaeza pedrobaeza deleted the 18.0-FIX-base_search_custom_field_filter branch February 10, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants