where put extended filter for tab....

[SledgehammerPL]

I want to have a filter in tab - it is quite easy - you have to edit controllers/XXX/config_relation.yaml and add filter: e.g:

organ_members:
  label: Skład
  view:
     list: $/party/structure/models/organmember/columns.yaml
     toolbarButtons: false
     showSearch: true
     scope: allTime
     filter: config_filter2.yaml
  manage:
     list: $/party/structure/models/person/columns.yaml
  pivot:
     form: $/party/structure/models/organmember/fields.yaml

and in config_filter2.yaml:

scopes:
  organ_member_valid_from:
    type: date
    label: stan na dziś

But I want more complex filter. Normally I use

 public function listFilterExtendScopes($filter)
    {
      $filter->addScopes([
        'my_advanced_filter' => [
          'label' => 'Stan na dzień',
          'type' => 'date',
          'conditions' => "very complex sql",
          'default' => Carbon::now()
        ]
      ]);
    }

But it works in normal columns executed by controller. Not in tabs in form...

So WHERE!? I tried to put it in all related controllers and models. And even formFilterExtendScopes.... Nope. Wrong place:

Undefined array key "my_advanced_filter"

[LukeTowers]

@SledgehammerPL

public function relationExtendViewFilterWidget($filterWidget, $relation, $model)
{
    $filterWidget->addScopes([
        'my_advanced_filter' => [
            'label' => 'Stan na dzień',
            'type' => 'date',
            'conditions' => "very complex sql",
            'default' => Carbon::now(),
        ],
    ]);
}

[LukeTowers]

Because you are extending the functionality provided by the RelationController behavior which is implemented by your controller class; your controller class is where you put it. See https://wintercms.com/docs/backend/relations#extend-relation-behavior.

[SledgehammerPL]

I do something wrong - I put it everywhere - to both controllers and both models... Still undefined array key

[LukeTowers]

I don't understand what you're asking. If you don't understand where it goes, don't just take the shotgun approach of putting it everywhere, that's just going to make your code a mess, hard to deal with, and cause issues.

I recommend you take some time if you haven't already to read through that documentation page in its entirety and then give it another try.

[SledgehammerPL]

I know where it should be. But if it doesn't work i understand that i'm not a super master - so i check if i'm wrong. Other filters (attached to controller works like perfectly). Scope (defined also in config_relation is defined in related model - that's why i'm really not sure where relationExtend should go...

(and to shotgun - when I hit the right place I would remove it from everywhere :D

[SledgehammerPL]

I found the inconsequence in config_filter.yaml - different for relation scopes and different for list scopes - opposite - > look at answer...

[SledgehammerPL]

Found it. It is very strange. But - if you made listFilterExtendScopes - you have to create config_filter like this:

scopes:
   my_filter:

if you use just:
scopes:

no filter appears

BUT
in relationExtendView - the opposite!

if you use:

scopes:

everything works

but if you use:

scopes:
  my_relation_filter:

Undefined array key "my_relation_filter" error appears