Hi all,
i have the following situation - a Insight Custom Field with reference typ - inbound connections, this is working well, but additionaly i wanna use the "Additional Filter Scope (IQL)" to filter the visible/chooseable entries based on another Insight Customfield (selected in the same Service Desk Request. I tried the following:
Were "Application" is the Name of the other Insight custom field...
...with the result getting this Error Message:
Error
<iql,Placeholder not supported in current context.>
Is there another way to make such a filter?
Thank you in advance
Regards Marco
Hi,
We are trying to achieve something almost the same, just putting the additional placeholder condition in the Filter issue scope.
But I do not understand the logic of why this should be a problem. If I create a regular Insight field, I can put several placeholders: "Change type"=${Change type} and "Categorie"=${Application type} in the filter issue scope condition. And it works like my field is dependant on two other fields. So, I don' see why it is a problem to add the same logic in a Referenced insight field. You have one reference that is always in place (Referenced field) and you add a condition in a context that narrows down the search depending on an issue field.
So, if it is applicable, make a regular insight field with Issue Filter of two placeholders?
Cheers,
Marina
Hi Marina,
tried the same in the Filter Scope field - same error -
Error
<iql,Placeholder not supported in current context.>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marco Hasenfratz ,
unfortunatelly I don't think this is possible. AFAIK there can be only one parent custom field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.