20 results for "how-to/dynamically-populating-list-webforms"

Dynamically populate value lists by information from other conditions

/how-to/dynamically-populating-lists-mvc

Suppose we have a database with Customer entity which has Country and City attributes. For both these attributes we define the value editors which return the lists of available values (countries and cities correspondingly). Now let's imagine the user adds a condition with the Country attribute e.g. Hera the steps needed to implement such a functionality: Define a value editor for the City attribute as SQL LIST with Cities.@{{Customer.Country}} list name (here Customer.Country is the ID of the Country attribute in the Customer entity). Let's name it "CitesSqlValueList") and then in a value list resolver modify its SQL according the currently selected country and get the list of values using GetValueListAsync method of EasyQueryManager class: What's happening here.

Building data model dynamically by DB meta-information

/how-to/build-data-model-by-db-meta-information

It's easier to fill your model right in the code directly from your database, using meta-information

Creating data model dynamically with code

/how-to/create-data-model-dynamically-with-code

-Data Model- object is an essential part of EasyQuery framework. However, sometimes you need to add some entities, entity attributes or operators to the existing model or to fill it from scratch using DB metadata information got from another source. In these cases, you can use EasyQuery API to build the model dynamically. Finally, we add entities and entity attributes. Here is an example of creatin a small data model: two tables (Customers and Orders) with one link between them, 2 entities (Customer and Order correpondingly) and a few attributes in each entity.

Building dynamic queries with EasyQuery and Entity Framework

/tutorials/dynamic-queries-with-easyquery-and-entity-framework

Here we describe how EasyQuery helps to implement a query building UI for creating custom, dynamic queries in .NET projects which use Entity Framework (6.x)

Getting started for ASP.NET WebForms

/version-3-x/getting-started/asp-net-webforms

Here you can find the instructions how to add EasyQuery components into your ASP.NET WebForms project

Upgrading to 5.x: ASP.NET (MVC and WebForms) projects

/upgrade-instructions/net-framework-3-x-to-5-x-/asp-net-mvc-webforms

This tutorial describes how to upgrde your old ASP.NET MVC project with EasyQuery 3.x to EasyQuery version 5.2.0 (or higher). 1.2 Use NuGet Package Manager to install the following packages: Korzh.EasyQuery.AspNet4 Korzh.EasyQuery.EntityFramewok6 - if you are using Entity Framework 6.x Korzh.EasyQuery.DataExport - if you will need the data exporting functions Korzh.EasyQuery.MsSqlGate (or .MySqlGate or .OdbcGate depending on your DB) - if you need to load your model directly from DB connection. Finally, we need to make some modifications on our pages where we use EasyQuery scripts. Version 5.2.0 and higher of EasyQuery scripts will not need JQuery anymore, so you will be able to throw them away if they are not used in your own pages. Here is an example for "advanced search" view: To update your Web Forms page your will need to do the following 3 steps: Add EasyQuery scripts and styles on your page.

Getting started for ASP.NET 4

/getting-started/asp-net-4-mvc-or-webforms

Describes the steps you need to perform for applying EasyQuery ASP.NET to your MVC or WebForms project

Dynamic queries for ASP.NET Core projects with Entity Framework Core

/tutorials/dynamic-queries-ui-aspnet-core-entity-framework

It takes a few minutes to add a new page with all necessary UI for building dynamic queries and to setup a middleware that will process all requests from that page, convert those request to the queries to your DB and return the result set back for visualization. This step is necessary to get the trial keys for EasyQuery framework. One for ASP.NET Core packages and another one - for EasyQuery.JS scripts. To simplify this task EasyQuery includes a Razor UI library package ( Korzh.EasyQuery.RazorUI ) that contains several predefined pages which you can use in your projects. For example, there is an "advaced search" page which is available via /EasyQuery/AdvancedSearch .

EasyQuery ASP.NET - using jQuery widgets on WebForms project

/getting-started/sample-webforms-javascript-webservice

In this article, you can find the instructions how to replace native WebForms with our jQuery widgets, with extract examples

Introduction to value editors

/fundamentals/about-data-editors

For example, value editor allows you to define a list of available values - so your users will be able to select the value from a drop-down list. "Custom list" value editor raises an event which can be processed either on the client-side or on the server. All other editions of EasyQuery (WinForms, WebForms, WPF or Silverlight) has ListRequest event in QueryPanel control which is raised when a user adds an attribute (or operator) with Custom List or SQL list value editor assigned to that attribute/operator. Here we show how you can filter the returned list according to the value specified for some other attribute. If such condition is defined - we get the value (country code) from it and use that value as a filter for the list of regions.

Version 5.2 release notes

/release-notes/version-5-2

Version 5.2 of EasyQuery not only brings some improvements to the .NET Core edition, it;s also the first release of 5.x branch for all other editions of EasyQuery which uses on .NET Framework 4.x and still were on 3.x branch until now: WinForms, WPF and ASP.NET 4 editions. There are 2 big changes in ASP.NET edition of EasyQuery which affects your MVC project when you upgrade to EasyQuery version 5.2.0 or higher. Starting from version 5.2.0 EasyQuery for ASP.NET uses the latest version of the client-side library (EasyQuery.JS 5.1.8 for now) which is the same that is used in ASP.NET Core edition. The same as for MVC applications, for WebForms we now use the latest version of EasyQuery.JS library on the client-side and a WebAPI controller on the server-side. Bug fixed: Disabled columns were included into GROUP BY section Bug fixed in WPF edition: Empty column title on edit Bug fixed in WPF edition: Wrong behavior of "Duplicate condition" operation If you are upgrading from version 5.x for ASP.NET Core - you just need to change the version numbers of all EasyQuery NuGet packages you are using to 5.2.0 and the version of the EasyQuery script files (or NPM packages) to 5.1.8 NB : For the users of EasyQuery script bundles (like eq.all.min.js ) published on our CDN You will also need to modify the full path to the EasyQuery classes and add ui namespace to it.