EasyQuery components need a [data model](/$aid/03bc06b0-83ec-4040-97ef-a50ca004177f) (a user-friendly representation of your DB) for their work. There are several different ways to create the model and load it on your project's startup. This article will describe all of them in detail.
Problem All EasyQuery demos works with one data model (and one database which corresponds to that model). However, some application might work with several databases and switch between them at run-time. The good news: starting from version 5.1.0 EasyQuery makes the task of switching between several data models quite simple.
Prerequisites Let's suppose we have: an ASP.NET Core project where we use Entity Framework Core to works with some database Pretty usual, yeah? Objectives We want: to create a view/page where our users can build custom (not predefined) queries to that DB and ... to run those queries over our DbContext to get the result sets. Solution
Localization / internationalization tasks for EasyQuery widgets. How to add new locale, how to set current locale, how to switch widgets language on-the-fly.
The tutorials for version 3.x branch of EasyQuery library
Detailed instruction on how to perform additional functionality while dealing with EasyQuery results.
This article shows how to add new clauses into the query and how to manage it
Paging can make your work with query more convenient. And here is detailed instruction on how to use it.
How to deal with lookup fields in EasyQuery
This article shows how to implement some particular tasks with your query
Here you can find all information needed to execute this task
Virtual attributes: what are they for and how to add one
Gridview filtering with EasyQuery ASP.NET (WebForms)
Sometimes it's necessary to attach some additional data with each query and use that data on query execution. For example, user might want to specify some piece of text on the client-side and filter the result set on that text so only the rows that contains that text must be inlcuded in the result. To add some extra data you can use beforeExecuteQuery event handler which can be defined on view initialization: Now if you check in Developer Tools (on Network tab), each .../execute request now includes ad additional data object in the request payload. Now to process this additional request data you can create your own implementation of EasyQueryManager and override its ExecuteQueryCore method. Here is an example: Here we just reconfigure our current query and add in it an additional condition group with a bunch of conditions like SomeColumns contains 'filter text' Finally, you need to register your manager class on EasyQuery middleware initialization:.