I have a Math Expression ($field_a - $field_b) that I want to create an exposed grouped filter for (select-list) so that I can effectively filter out my results.
How can I set this up so that users will be give two options based on the values of two field?
I ended up creating a custom field handler for this purpose.
Related
I'm building a dash using Data Studion and I need to create a custom query using CASE WHEN statments. The problem is that the conditions must be the values selected through a filter. How can I get the value selected on the filter and use it as a parameters on my query?
you can not , the only parameter that can be passed from a filter is dates as per this documentation https://support.google.com/datastudio/answer/6370296?hl=en
all you can do is vote for this feature request
https://issuetracker.google.com/issues/142183085
So i am using graphql feature in Orchard to get data from the events type,
each eventsItem has a bag of Event as it shows the image bellow
So the problem is that i need to fetch an event with its "contentItemId",is there a way to add where clauses in an inline Fragment.
Fragments are just a way to specify the selection set (i.e. fields) by type at runtime. They are not a way to filter results. GraphQL does not provide any built-in way to filter, sort or otherwise mutate the results -- it's up to each individual service to implement those features. If the schema doesn't expose any argument on the events, bag, or contentItems fields to let you do the sort of filtering you're trying to do, then it's not possible to do so through a query.
I have a status field in my elastic search index which can take values Open,Closed,Clear,Intermediate,Ready for Approval. Right now, I have created a visualization and sorted this field descending based on the Term. What I want to achieve is - I want this to be sorted in this particular order Open,Clear,Intermediate,Ready for Approval,Closed.
How do I achieve this? One option I am thinking is creating a scripted field and prefixing with integer column, but I am not sure if I will be able to filter the visualization later?
If this list of possible values is a static list of known values, there is another way to define your visualization with a little more manual configuration. Just replace your terms aggregation with a filters aggregation and add custom filters for the possible values like so:
Kibana will respect the order of your filters in the visualization. From a performance perspective, this should also be better than using a scripted field...
I am using two different indexes which are named cdr_mobile and cdr_volte that have lots of common fields. So in order to show datas on Kibana I have made an alias using two of them cdr_alias and now I am using cdr_alias in order to retieve data to Kibana.
The problem I have is, I cannot demonstrate common fields on the same column. Instead of that I am having for example, cdr_volte.startOfCharge and startOfCharge (the other thing I dont understand is here, it is using the cdr_mobile as default).
Do you have any idea how I can put the common fields on the same column ?
Thank you
I have made an error on mapping, In order to put same fields on the same column you must have exactly same mapping for the field for both indices.
I have a search page with multiple search options(input text boxes) Based on the search criteria entered , I need to create a dynamic search query. (I need search results based on the fields for which user inputs some value)
or you can use <af:quickQuery> for a simple search. Here's the sample code taken from Oracle demo.
<af:quickQuery label="Search" id="search" searchDesc="search" binding="#{editor.component}" value="#{demoQuickQuery.queryDescriptor}" queryListener="#{demoQuickQuery.processQuery}">
</af:quickQuery>
If you are using ADF/BC, this is built-in. Just use the <af:query/> component.
af:query is the more robust of the two query components, but does require you create a viewcriteria object in the VO that will be the basis for the query. However it is very powerful: dynamically add new attributes to the query at runtime, change query rules (starts with, contains, etc)
af:quickquery allows you to choose one and only one attribute to query on at a time.
Please note: these components (and the executewithparms) are the only supported query methods in ADF Faces 11g