Thanks @BastianHammer thats the tutorial I was following. It doesnāt work.
Also there is no āMultiRelateā field type, unless itās strictly created by code. I assume they mean from a subpanel, not a relate type field. The documentation is really hard to understand.
Yes, the new field types are missing in the studio.
Iāve built them just via code and/or own modules to load them later on.
Hope this will be āfixedā sooner or later, otherwise all the new features and usefulness is restricted to developers only and the target audience of SuiteCRM is shrinking quickly.
As for the documentation: it doesnāt lead to a solution of this topic, but in general - if you turn it around, donāt have a specific goal in mind and just start copying / tinkering the tutorials and then see the outcome, that often works.
Itās a different approach - not so much a guide to a specific solution but more sth. like getting to know what could be done with the system in general. Not always helpful and difficult to interprete / find use for.
This was a very useful developer feature in SuiteCRM 7. Hopefully, it will be added soon. Being able to filter the relate field popup is such a great feature for UI.
I had the exact same working in V7, and for now like you, impossible to make it work in V8. Iāve tried to edit the detailviewdef or editviewdef, for now I didnt find how to do this
Hi @adam_2 , I ran into the same issue on SuiteCRM 8.6 and can confirm that initial_filter doesnāt work in the new (Angular) frontend popups. It seems this is still only supported in legacy (SuiteCRM 7-style) views.
As a workaround, I had some success using the newer filter option in field metadata, for example:
This works for certain field types (like MultiRelate) in the v8 frontend, although itās not a full replacement for initial_filter in popup selections.
For now, it looks like thereās no direct equivalent for setting an initial popup filter in SuiteCRM 8, so the options are either:
Use the filter metadata where applicable
Rely on saved/quick filters in the UI
Or implement a custom backend workaround (less ideal)
Would be great if this gets proper support in a future release.