Filtering NReco.GraphQL documentation

Filters allows us to constrain queries to a particular account, requests by date or set logical conditions which exposes Boolean algebra on nodes. Without filters, queries can suffer performance degradation, results can easily be enormous and using is fulled by pain.

Filter configuration

"Options": {
	"Filter": {
		"Key": "filter_jsonstyle",
		"RelexKey": "new_filter_relex",
		"Enabled":true
	}

An example of using standard filter

query {
	orders(filter:{
			incidentid_in:[426],
			OR:[
				{validityend:null},
				{validityend_gt:"2021-08-27"},
				{
					AND:[
						{validityend_eq:"2021"},
						{approved_neq:"Yes"}
					]
				}
			],
			status_in:["Approved","InProgress"]
		}) 
	{
		orderId
		status
	}
}
		

{
	"data": {
		"orders": [
			{
				"orderId": 1006,
				"status": "Approved"
			},
			{
				"orderId": 1106,
				"status": "InProgress"
			}
		]
	}
}
		

Inside filter argument you can:

use any of defined schema's fields (name should be the same as it defined in the json) which are ended with of postfixes:

like determines whether a specific character string matches a specified pattern (filer value can contain the percent sign "%" - it will be applied SQL-operator in the WHERE clause)

nlike not like (the same as previous but negate)

gt greater than

lt less than

geq greater or equal to

leq less or equal to

neq not equal

in in (array)

nin not in (array)

Use the AND/OR operators to create and/or combine multi-node filter

An example of using alternative, relex-based filter

query {
	orders(filter_relex:"orderId >= \"1000\" AND ShipCountry IN \"Brazil,Mexico\":string[]") {
		orderId
		ShipCountry
	}
}
		

{
	"data": {
		"orders": [
			{
				"orderId": 10276,
				"ShipCountry": "Mexico"
			},
			{
				"orderId": 1106,
				"ShipCountry": "Brazil"
			}
		]
	}
}