Custom primary filter for multi-enum

[rabii]

I have created a custom primary filter but it is not working, i don't know how to get values for a multi-enum field, below code doesn't work. anyone knows how to get value for multi-enum field using the SelectBuilder :

<?php

namespace Espo\Custom\Classes\Select\Account\PrimaryFilters;

use Espo\Core\Select\Primary\Filter;
use Espo\ORM\Query\SelectBuilder;

class Clients implements Filter
{
public function apply(SelectBuilder $queryBuilder): void
{
$queryBuilder->where([
'companyType' => ['Client', 'Introducer'],
]);
}
}

the companyType is a multi-enum field so i am trying get the companyType values both Client and Introducer.

Thanks

[emillod]

Hello rabii

please use this:

$queryBuilder->where([
'status=' => ['Active', 'Closed']
]); 

You simply forgot about sign = next to field name

[espcrm]

I don't see the difference between yours code (symbol) and his.

His "=" sign is same position as yours, everything else seem same also.

[emillod]

espcrm he posted
'companyType' =>

And mine example:
'status=' =>

[espcrm]

I mean that just fieldname isn't it? Otherwise the 'syntax' is all good like yours... My coding skill is next to the trash can so I can't tell where the error is.

UPDATE: OK, I totally didn't see that double = sign.

[item]

Hi,
your sample is for enum field, not for multi-enum
see on GitHub closed issue where Yuri have post solution

https://github.com/espocrm/espocrm/issues/2268

[emillod]

you right. I'm sorry. I didn't noticed that.

[rabii]

item thanks for your reply i already tried your solution before posting here and it didn't work because that solution would only work for enum and in my case i am using multi-enum which treated differently, big thanks to yuri who helped me sort it out, there are two ways to achieve this see both code below:

<?php

namespace Espo\Custom\Classes\Select\Account\PrimaryFilters;

use Espo\Core\Select\Primary\Filter;
use Espo\ORM\Query\SelectBuilder;
use Espo\Core\Select\Where\ConverterFactory;
use Espo\Entities\User;

class PartnerClients implements Filter
{
private $converterFactory;
private $user;
public function __construct(ConverterFactory $converterFactory, User $user){
$this->converterFactory = $converterFactory;
$this->user = $user;
}
public function apply(SelectBuilder $queryBuilder): void
{
$converter = $this->converterFactory->create('Account', $this->user);
$whereClause = $converter->convert(
$queryBuilder,
(new \Espo\Core\Select\Where\ItemBuilder)
->setAttribute('accountType')
->setType('arrayAllOf')
->setValue(['Client', 'Introducer'])
->build()
);
$queryBuilder->where($whereClause);
}
}

Second way to achieve this below (both ways works) - second way allow to give more specific conditions e.g only accountType (Introducer):

<?php

namespace Espo\Custom\Classes\Select\Account\PrimaryFilters;

use Espo\Core\Select\Primary\Filter;
use Espo\ORM\Query\SelectBuilder;
use Espo\ORM\Query\Part\Condition as Cond;

class OnlyActiveIntroducers implements Filter
{
public function apply(SelectBuilder $queryBuilder): void
{
$introducer = SelectBuilder::create()
->from('ArrayValue')
->select('entityId')
->where([
'value' => 'Introducer',
'attribute' => 'accountType',
'entityType' => 'Account',
'deleted' => false,
])
->build();

$notClient = SelectBuilder::create()
->from('ArrayValue')
->select('entityId')
->where([
'value' => 'Client',
'attribute' => 'accountType',
'entityType' => 'Account',
'deleted' => false,
])
->build();

$notAccountant = SelectBuilder::create()
->from('ArrayValue')
->select('entityId')
->where([
'value' => 'Accountant',
'attribute' => 'accountType',
'entityType' => 'Account',
'deleted' => false,
])
->build();

$queryBuilder
->where(
Cond::and(
Cond::in(Cond::column('id'), $introducer),
Cond::notIn(Cond::column('id'), $notClient),
Cond::notIn(Cond::column('id'), $notAccountant),
Cond::in(Cond::column('state'), ['Active']),
)
);
}
}

I hope this help someone.
Thank you guys for your support, i love this community.

[item]

Yes, it will help many

[bandtank]

rabii How does this filter fit into the entire process? What calls it? Is it automatically used or is there more code in another file? Also, what does it do?

I'm wondering if this is a special namespace: Espo\Custom\Classes\Select\Account\PrimaryFilters

[rabii]

Hi @bandtank

The filters allow you to have primary filter on list view of certain entity. it is powerful way to filter data based on conditions also you can add more user restrictions if you wish to. using advanced pack you can build filter reports but i prefer to use these custom filters as i can use them on dashlets as well. you can find the whole process of creating custom filters on this blog post here https://devcrm.it/custom-filters

i hope you find it helpful if you need it in future.

[item]

Hi bandtank,

https://docs.espocrm.com/development...erclassnamemap

in V6? or V7 Yuri have do so

[bandtank]

Hi bandtank,

https://docs.espocrm.com/development...erclassnamemap

in V6? or V7 Yuri have do so

I do not know what to do with the information at that link. I found it, but how is it implemented? Which files? The information is helpful, but only if you already know what to do. A complete guide would be better and I think it would only be a few sentences to explain the details.

[item]

first Hi, (with my poor english)

https://github.com/espocrm/espocrm/blob/master/application/Espo/Modules/Crm/Resources/metadata/selectDefs/Account.json

in metadata you declare wich and where you select class is

then in path of rabii have posted, you implement ...

and for language file.. i don't know but easy to find..

I use on github "search/find" .. and try to replicate

[bandtank]

first Hi, (with my poor english)

https://github.com/espocrm/espocrm/b...s/Account.json

in metadata you declare wich and where you select class is

then in path of rabii have posted, you implement ...

and for language file.. i don't know but easy to find..

I use on github "search/find" .. and try to replicate

Thanks. That helps a lot, actually. I don't see a need for primary filters after looking at the code in the repository because the advanced pack allows reports to be used as filters. It's good to know how to do it, though.