Hi Dojo,
as was already asked here last year and at another occasion the year before, there are use cases for which the filtering of parameters of a child element in a service template based on the use of a foreign key would be very handy to have.
It's possible to use the primary key by starting the filter with ^pk^, but the self-suggesting use of ^fk^ does not lead to the result I hoped for (which is the filter being applied on the foreign key).
So basically: has this become possible in the meantime in any other way, or is this on the road map to be implemented?
We have the use case that parameters/rows from different tables are logically linked to entries of another table by a common foreign key (which corresponds to the primary key of said parent table), but we cannot apply the proper filtering to include all these parameters of interest in the service.
Thanks a lot!
Hi Nils,
I think the main difficulty here is that a single table can contain multiple foreign-key (FK) relationships, each pointing to different parent tables.
Because of that, the Service Template engine has no clear way to determine which FK relation should be used for filtering when several exist in the same table.
This is my guess as to why filtering on FKs isn’t currently implemented.
Kind regards,
Hi José,
thanks for your assessment! So far this makes sense… however, I'd hope that there is some workaround or solution possible.
Best regards
Nils