Upgrade instructions

Data Model Editor

About Data Model Editor

Here you can find detailed information about this instrument and guideline, how to use it to perform all needed tasks.

Data Model

In short (and by its name), data model - is a model (representation) of some data stored in your database. It solves two major problems: Presents the data to the end user in a more friendly and familiar way. Contains some meta information that helps EasyQuery components to build query statements in SQL or other query languages. Any data model contains the following main sections:

Upgrade instructions. From Version 3.x to 5.x for .NET Framework 4.x projects

Upgrade instructions: Version 7.0

You just need to update the version of all EasyQuery packages (except Korzh.EasyQuery.MsSqlGate - see the details below) to 7.0.x (whatever the latest version is there at the time of your reading). For example: should be changed to: As for Korzh.EasyQuery.MsSqlGate package, it was renamed to Korzh.EasyQuery.SqlServerGate (to prevent any confusion with Korzh.EasyQuery.MySqlGate ). Here are examples: Before EasyQuery 7.0: EasyQuery 7.0+ Both functions accepts a delegate with EasyQueryOptions parameter, so no changes here. Here are some examples: In the most cases, your client-side code and markup will not need a lot of changes with version 7.0 of EasyQuery.JS. Here are the thins that require your attention: If the license key for EasyQuery.JS is hardcoded in the page's script as a parameter of useEnterprise(...) call (like view.getContext().useEnterprise('YourEasyQueryJsKeyGoesHere') ) you will need to get a new one for version 7.0 and replace it there.

Upgrading from version 3.x to 4.0

How to upgrade your project from version 3.x to version 4.0 of EasyQuery

Upgrading from version 2.x to 3.0

How to upgrade your project from version 2.x to version 3.0 of EasyQuery

Value Editors

Here you can find the full list of editors and choose any you need in your work with Data Model:

Upgrade instructions: EasyQuery.NET 5.3 + EasyQuery.JS 6.0

If you use EasyQuery.JS via NPM packages (for example, in your Angular or React project) you need to do the following changes: Since JQuery is not used anyore, you can remove @easyquery/ui-jquery package from your project. All functionality from this package was moved either to @easyquery/core or @easyquery/enterprise packages. Add @easyquery/enterprise package if you need full set of features as in previous version (5.1.x) of EasyQuery. Obviously, set the version number for all EasyQuery packages to 6.0.0 (or higher). Get the license key for EasyQuery Enterprise.

Upgrading from version 4.x to 5.x

Here you will find step-by-step instructions on how to upgrade your current ASP.NET Core project that uses version 4.x of EasyQuery to version 5.0

Edit link dialog

Here you can find all necessary information of how to edit link dialog and how to add new conditions.

Upgrading to 5.x: WinForms and WPF projects

This tutorial describes how to modify your old Windows Forms or WPF project with EasyQuery 3.x to upgrade to EasyQuery version 5.2.0 (or higher). Please note. Version 5.2.0 of EasyQuery works only on .NET Framework 4.6.1 or higher. So, if your project targets a lower version of .NET Framework - you will need to update Target Framework for your project first (right-click on the project in Solution

Navigate through data model entities and attributes

A code snippet which demonstrates how to run through data model entities and attributes

Entity class

Represents one entity

Entity class

Represents one entity

Entity class

Represents one entity

Entities page

This page describes entities participating in the data model and their attributes.

Aggregate data

From this article you will see how to aggregate (count, sum, etc.) data in your queries.

Working with several data models

All EasyQuery demos works with one data model (and one database which corresponds to that model). Here we are going to describe how to add a selector that switches between two data models on your view/page and then how to setup a custom "model loader" to handle GetModel requests propertly. To make it possible to switch between these two models we need some selector element on our page. The only problem here - is to switch the database connection accordingly the the switches between the models. Now when the user selects an item in our model selector element on the client-side - our server-side code automatically loads the selected model and connects to a proper database (when necessary)..