Restricting object relation selection list based on the calling object type.

[MarkusHolstein]

Hi all,

we have multiple object types, which behave to some extend the same.
Those are ProductTypeA and ProductTypeB.
Both contain a "many-to-one relation field" to CategoryType type.

CategoryType types can get quite a big number. But for the sake of example we have Category1, Category2, Category3.

Is there a way, that I can restrict the usage of CategoryTypeA in those ProductTypes, so that in objects of ProductTypeA all CategoryType objects are allowed and in ProductTypeB only Category1 and Category2 can be selected?

Thanks in advance
Markus

[AndrewKMoses]

I would suggest to do the check in a preadd / preupdate event listener.

[MarkusHolstein]

It would be better for the user, if the objects were already filtered by allowed values. Otherwise he would add the category, change some other values and then there would be an error quite late in the process. Additionally, it might be hard to guess, which objects might be allowed and which not, if this is a multiple category-field :-(

So I would rather hope for another solution for filtering the list.
But thanks for that suggestion anyway.

[SimonCremer]

We have a similiar requirement which was easy to solve in AdminUI, but it is not in Studio UI (https://github.com/orgs/pimcore/discussions/19169).
If you find a solution please share it with us. I will do the same if I can solve this problem.

[MarkusHolstein]

Hi @SimonCremer, since I am no React-developer I let AI implement a frontend override, that adds some context about the current class to the request, when fetching the target relation object classes. and adding a custom webpack entrypoint.
The filtering itself is easy in php with tagging a class with pimcore.studio_backend.search_index.data_object.filter and implementing the interface Pimcore\Bundle\StudioBackendBundle\DataIndex\Filter\FilterInterface