TYPO3 Core

What do you mean "having both"? Is there a way to hide the normal selector box? I always have both.

My use case is mostly group-type fields related to tables with lots of entries, where it's really not possible to make choices in the selector.

Yes, a filter box above the selector would be better, but that doesn't exist in the Core AFAIK. Or did I miss something?

OK, sorry about the "both" thing. I now see in another project quite a few fields with just the wizard. I can't access the other project right now, but I think there's some customization done on the selectors, so that's maybe why we have the selector and the wizard.

Anyway the problem remains that the suggest wizard does not work like the selector and IMO the suggest wizard is wrong. It should not be necessary to have access to some records to be able to make relations to them. Of course, this is debatable. Maybe it should be a configuration option.

I would guess there's a fair chance that the problem still exists, but I can't remember what was my use case anymore, so I can't check. I think this can be closed for now, although I wouldn't consider it as resolved.

I know the problem always exists, also in TYPO3 7.2

Use-Case

Extension X provides Person Data like employees
Extension Y is for Joboffers, here i have a mm-relation to select an employee for a joboffer as contact person.

Both Extension-Data are stored in different sys_folders

Content Manager for Joboffers have access only to sys_folder with joboffer-data.
In the mm-selectboxes he can see als employees and select some employees as contact.
This field also has the suggest wizard, but if the content-manager type in a search, he got no results.

So i think suggest and select should have the same access rights.
It would be great to have a switch (respect access rights or no) for both

Best Regards Roman