By default, XAF doesn't execute the first navigation item when changing the group. But, you can easily change this behavior by customizing the navigation control, and reusing the functionality of the ShowNavigationItemController.

This example demonstrates how to write a controller that will do this. This controller is managed by the attribute. By default, it doesn't select the first navigation item in the group.

These help topics will be also very helpful:
How to: Change Navigation Control Appearance
ShowNavigationItemController Class
Built-in Controllers and Actions

When ASPxGridView is bound to a server mode data source, all data operations are performed on the database server: Binding to Large Data (Database Server Mode)?. Thus, results depend on database settings. For instance, filtering data with diacritic signs depends on the default collation of your data server:
[CodeProject.com] Configuring SQL Server Accent-Insensitivity
[Stackoverflow.com] Questions about accent insensitivity in SQL Server (Latin1_General_CI_AS)?

In other words, the first solution to achieve accent-insensitive filtering when the grid is bound to the server mode datasource is to change collation on the server. 
Another solution is to create a custom filter operator by implementing ICustomFunctionOperator and  ICustomFunctionOperatorFormattable interfaces and modify a filtering request to the database in the ICustomFunctionOperatorFormattable.Format method:

[C#]
stringICustomFunctionOperatorFormattable.Format(TypeproviderType,paramsString[]operands){varoperand=string.Format("N'%{0}%'",operands[0].Split('\'')[1]);returnstring.Format("{0} COLLATE SQL_Latin1_General_CP1_CI_AI LIKE {1} ",operands[1],operand);}

[VB.NET]
PrivateFunction ICustomFunctionOperatorFormattable_Format(ByVal providerType As Type, ParamArrayByVal operands() AsString) AsStringImplements ICustomFunctionOperatorFormattable.FormatDim operand = String.Format("N'%{0}%'", operands(0).Split("'"c)(1))ReturnString.Format("{0} COLLATE SQL_Latin1_General_CP1_CI_AI LIKE {1} ", operands(1), operand)EndFunction

In this case, the accent-insensitive collation is applied only for filtering. Note that this approach is not supported by LINQ-based ORMs.

This example demonstrates how to implement accent-insensitive filtering in Auto Filter Row when ASPxGridView is bound to XpoDataSource with Server Mode enabled. To test the example, download the solution to your local machine.

See Also:
How to make the Grid's filter to be a case- and accent-insensitive in Server Mode
E4836: How to create a custom ASPxGridView's filter insensitive to the number of spaces and punctuation

This example is an illustration of the K18561: Using jQuery / jQuery UI libraries with DevExpress ASP.NET Controls / MVC Extensions KB Article. Refer to the Article for an explanation.

This example illustrates how to attach jQuery selectors to ASPxGridView DataCells' content and keep selectors' functionality after grid's rendering is completely updated via a callback.

Usually when it is necessary to attach jQuery selectors to any existing HTML content, it is recommended to use the $(document).ready function that can be used for handling the state when the DOM is fully loaded. When some jQuery selectors are attached to the HTML content inside ASPxGridView, these selectors are stopped after the grid's rendering is completely updated via a callback (and the entire grid's HTML content is re-created on the client side). It is necessary to execute the required jQuery selectors explicitely by handling the client-side ASPxClientGridView.EndCallback event that is raised on the client side after a callback's server-side processing has been completed. It is also recommended to handle the client-side ASPxClientControl.Init (ASPxClientGridView.Init) event (rather than the use of the jQuery $(document).ready function) to enure that the corresponding client-side control's programmatic object is initialized.

Refer to the Client-Side Functionality Overview topic in our documentation to learn more about the common concepts of the client-side API of the DevExpress ASP.NET Controls.

This example illustrates how to add MVVM capabilities to the Master-Detail functionality. In this example we have created the MasterDetailMVVMHelper class that introduces the ExpandedMasterRowsSource attached property. This property is intended to be attached to GridControl and allows controlling details' expanded state via a collection in a view model.

Here is a sample XAML that illustrates how to attach this property to GridControl and make it bound to the ExpandedItems collection:

[XAML]
<dxg:GridControlmy:MasterDetailMVVMHelper.ExpandedMasterRowsSource="{Binding ExpandedItems}"Name="gridControl1"ItemsSource="{Binding Data}">

 
Now, by adding a couple of data objects to the ExpandedItems collection, you can expand corresponding rows in GridControl:

[C#]
ExpandedItems.Add(Data[1]);ExpandedItems.Add(Data[10]);

[VB.NET]
ExpandedItems.Add(Data(1))
ExpandedItems.Add(Data(10))

An important note: The collection being bound to the ExpandedMasterRowsSource must be an implementation of the INotifyCollectionChanged interface, otherwise this functionality will not operate as expected.

This example shows how to dynamically add a parameter to XtraReport, compose FilterString in the SqlDataSource and use XtraReport's parameters to filter data in the SqlDataSource.

To add the capability to analyze data in your application, the eXpressApp Framework supplies the Pivot Chart Module. To have the Analysis functionality in an application, you should simply add this module and the built-in Analysis business class to the application. In this instance, the navigation control will contain the Analysis item and end-user will be able to create Analysis objects. However, you may need to provide the ability to create an Analysis object from any List View, setting the new Analysis object's ObjectType property to the object type of the List View. This example demonstrates how to accomplish this task.

For details, refer to the How to: Add the Analyze Action to List Views topic in XAF documentation.

[C#]
Anexceptionoftype'System.ArgumentException' occurredinDevExpress.ExpressApp.v16.1.dllbutwasnothandledinusercodeAdditionalinformation:Anerrorwithnumber 1096 hasoccurred.Errormessage:TheObjectSpacehasalreadybeenassignedtoanotherrootview:'DetailView,ID:Analysis_DetailView'.ThiserroroccursonlywhenyoutrytoassignanObjectSpacethatisalreadyusedbyarootViewtoanotherrootview.Forinstance,youmayreceivethiserrorwhenusingtheXafApplication.CreateDetailView/CreateListViewmethodsinaViewControllerandpassingtheView.ObjectSpaceobjectasaparametertothesemethodswhentheView.IsRootpropertyistrue.Toavoidthiserrorit'ssufficienttopassanewObjectSpaceinstancecreatedviatheXafApplication.CreateObjectSpacemethodinthesemethods,orcreatenon-rootViewsbypassingacorrespondingparametertothesemethods.

Scenario
This is a variation of the How to generate and assign a sequential number for a business object within a database transaction, while being a part of a successful saving process XPO example, which was specially adapted for XAF applications.

In particular, for better reusability and more smooth integration with the standard XAF CRUD Controllers, all the required operations to generate sequences are managed within the base persistent class automatically when a persistent object is being saved. For more developer convenience, this solution is organized as a reusable XAF module - GenerateUserFriendlyId.Module. This module consists of several key parts:

    - Sequence and SequenceGenerator are auxiliary classes that take the main part in generating user-friendly identifiers. Take special note that the SequenceGenerator.Initialize method must be called during your XAF application startup for the correct operation.

    - UserFriendlyIdPersistentObject is a base persistent class that subscribes to XPO's Session events and delegates calls to the core classes above. Normally, you must inherit your own business classes from this base class to get the described functionality in your project.

    - IUserFriendlyIdDomainComponent is a base domain component that should be implemented by all domain components that require the described functionality.

Check the original example description first for more information on the demonstrated scenarios and functionality.

Image may be NSFW.
Clik here to view.

Steps to implement
1. Copy and include the GenerateUserFriendlyId.Module project into your solution and make sure it is built successfully.  Invoke the Module or Application Designer for the YourSolutionName.Module/Module.xx  or YourSolutionName.Wxx/WxxApplication.xx files by double-clicking it in Solution Explorer. Invoke the Toolbox (Alt+X+T) and then drag & drop the GenerateUserFriendlyIdModule component into the modules list on the left.

2. In the YourSolutionName.Wxx/WxxApplication.xx files, modify the CreateDefaultObjectSpaceProvider method to call the SequenceGenerator.Initialize method as shown in the Demo.Wxx\WxxApplication.xx files:

[C#]
...protectedoverridevoidCreateDefaultObjectSpaceProvider(CreateCustomObjectSpaceProviderEventArgsargs){GenerateUserFriendlyId.Module.Utils.SequenceGenerator.Initialize(this,args.ConnectionString);//!!!...}

3. If you are using pure XPO classes, then inherit your required business classes from the module's UserFriendlyIdPersistentObject one and use the derived SequenceNumber property as required:

[C#]
publicclassContact:GenerateUserFriendlyId.Module.BusinessObjects.UserFriendlyIdPersistentObject{[PersistentAlias("concat('C', ToStr(SequentialNumber))")]publicstringContactId{get{returnConvert.ToString(EvaluateAlias("ContactId"));}}

If you are using DC, then implement the IUserFriendlyIdDomainComponent interface by your custom domain component:

[C#]
publicinterfaceIDocument:GenerateUserFriendlyId.Module.BusinessObjects.IUserFriendlyIdDomainComponent{[Calculated("concat('D', ToStr(SequentialNumber))")]stringDocumentId{get;}

Additionally for DC, use the UserFriendlyIdPersistentObject as a base class during your custom domain component registration, e.g.:

[C#]
XafTypesInfo.Instance.RegisterEntity("Document",typeof(IDocument),typeof(GenerateUserFriendlyId.Module.BusinessObjects.UserFriendlyIdPersistentObject));

For more information, download and review the Address, Contact, and IDocument types within the Demo.Module project. These are test business objects that demonstrate the use of the described functionality for XPO and DC respectively. A required format for the user-friendly identifier property in these end classes is defined within an aliased property (ContactId in the example above) by concatenation of a required constant or dynamic value with the SequentialNumber property provided by the base UserFriendlyIdPersistentObject class. So, if you need to have a different format, modify the PersistentAliasAttribute expression as your business needs dictate.

IMPORTANT NOTES

1. As an alternative, you can use a more simple solution that is using the DistributedIdGeneratorHelper.Generate method as shown in the FeatureCenter demo ("%Public%\Documents\DXperience 13.X Demos\eXpressApp Framework\FeatureCenter\CS\FeatureCenter.Module\KeyProperty\GuidKeyPropertyObject.cs" ) or at How to generate a sequential and user-friendly identifier field within a business class 
2. This solution is not yet tested in the middle-tier and SecuredObjectSpaceProvider scenario and most likely, it will have to be modified to support its specifics.
3. The sequential number functionality shown in this example does not work with shared parts (a part of the Domain Components (DC) technology) in the current version, because it requires a custom base class, which is not allowed for shared parts.

Scenario
In this example, it is demonstrated how highlight focused editors in an editable DetailView for both Windows and the Web:

Image may be NSFW.
Clik here to view.

Additionally, the following Model Editor extensions are implemented for more convenience:
 - The HighlightFocusedLayoutItem attribute at the Application | Options node level allows you to control this functionality globally per application via the Model Editor.
 - The HighlightFocusedLayoutItem attribute at the Views | DetailView node level allows you to customize only certain DetailViews via the Model Editor

Image may be NSFW.
Clik here to view.

Steps to implement
1. Modify YourSolutionName.Module/Module.xx file as shown in the WinWebSolution.Module\Module.xx file of this example.
Note: The approach from the eXpressApp Framework > Concepts > Application Model > Extend and Customize the Application Model in Code article is used here.

2. Copy the WinWebSolution.Module\HighlightFocusedLayoutItemDetailViewControllerBase.xx file into the YourSolutionName.Module project.
Note: The approaches from the eXpressApp Framework > Concepts > Application Model > Access the Application Model in Code and Controller.Active Property articles is used here.

3. Copy the WinWebSolution.Module.Win\WinHighlightFocusedLayoutItemDetailViewController.xx file into the YourSolutionName.Module.Win project.
Note: In Windows Forms applications, the functionality is provided with the help of the LayoutControl and its HighlightDisabledItem and AllowItemSkinning options. The approach from the eXpressApp Framework > Concepts > UI Construction > View Items Layout Customization article is used to access LayoutControl.

4. Copy the WinWebSolution.Module.Web\WebHighlightFocusedLayoutItemDetailViewController.xx file into the YourSolutionName.Module.Web project. Then copy the WinWebSolution.Web\E2106.js file into the YourSolutionName.Web project.
Finally, add the <script type="text/javascript" src="E2106.js"></script> line into the <head> element of your YourSolutionName.Web\Default.aspx file.
Note: In ASP.NET applications, the functionality is implemented manually as per How to highlight a focused editor via client-side scripting via client-side events provided by our ASP.NET editors. The approach from the eXpressApp Framework > Getting Started > Comprehensive Tutorial (MainDemo Application) > Extend Functionality > Access Editor Settings article is used to access PropertyEditor controls.

IMPORTANT NOTES
It is possible to register your JavaScript functions at runtime via the DevExpress.ExpressApp.Web.WebWindow.CurrentRequestWindow.RegisterXXXScript methods called from a Controller when it is activated or when page controls are created. Refer to the How to automatically refresh data in a View after a certain period of time on the Web article for an illustration of this approach.

This sample illustrates how to customize the wizard in the End-User Designer.

See also:
Data Source Wizard – How to Replace the Standard Query Builder
Data Source Wizard - How to customize the list of data providers

[VB.NET]
PublicFunction GetStaticPersons() As IList(Of Person)ReturnNew List(Of Person)({New Person() With {.FirstName = "John", .SecondName = "Abbot"}, New Person() With {.FirstName = "Paul", .SecondName = "Bass"}, New Person() With {.FirstName = "George", .SecondName = "Chance"}})EndFunction

Starting with v15.1, GridLookup can be automatically bound to a model field that returns an array of values (see  DevexpressEditorsBinder - Support binding multiple values selected in MVC editor extensions to a Model's collection-type property)
This example illustrates how to use GridLookup in a multiple selection mode (SelectionMode is Multiple) as a GridView editor. The main idea is to use the MVCxGridViewColumn.SetEditItemTemplateContent method to place GridLookup in EditForm. The same approach will work for a custom EditForm (GridViewSettings.SetEditFormTemplateContent) as well.

Note that prior to version 16.1.6, the GridLookupExtension.Bind method doesn't automatically select required keys. It's necessary to assign a delegate method to the PreRender property to manually select the values using the GridViewSelection.SelectRowByKey method. Starting with version 16.1.6, it is sufficient to pass values to bind/select to the GridLookupExtension.Bind method.

[C#]
//Prior to version 16.1.6 onlysettings.PreRender=(s,e)=>{MVCxGridLookuplookup=sasMVCxGridLookup;for(inti= 0;i<Model.TagIDs.Length;i++)lookup.GridView.Selection.SelectRowByKey(Model.TagIDs[i]);};

[VB.NET]
'Prior to version 16.1.6 only
 settings.PreRender = Sub(s, e)Dim lookup As MVCxGridLookup = TryCast(s, MVCxGridLookup)For i AsInteger = 0 To Model.TagIDs.Length - 1
                lookup.GridView.Selection.SelectRowByKey(Model.TagIDs(i))Next iEndSub

[C#]
publicActionResultGridLookupPartial(int?KeyParameter){varmodel=GetModelInstanceByKey(KeyParameter);returnPartialView(model);}

[VB.NET]
PublicFunction GridLookupPartial(ByVal KeyParameter?AsInteger) As ActionResultDim model = GetModelInstanceByKey(KeyParameter)Return PartialView(model)EndFunction

[C#]
@Html.DevExpress().GridLookup(settings=>{settings.Name=PropertyName;}).BindList(...).Bind(Model.PropertyName).GetHtml()

[VB.NET]
@Html.DevExpress().GridLookup(Sub(settings)
    settings.Name = PropertyNameEndSub).BindList(...).Bind(Model.PropertyName).GetHtml()

See also: 
GridView - How to use GridLookup with single selection mode in EditForm

Web Forms:
How to use two-way data-bound ASPxGridLookup in edit form of ASPxGridView to edit data
How to use ASPxGridLookup in multiple selection mode as the ASPxGridView editor

To localize DevExtreme widgets, do the following:

- Link required dictionaries as described in the following help topic:
Link Dictionaries

Note that the order of references is important.

- Reference the DevExtreme localization script:
Use Predefined Dictionaries 

- Initialize your application after setting the locale:

[JavaScript]
$.when(...}).then(
        Globalize.load).then(function(){
        Globalize.locale('de');// Initialize your application here
        ko.applyBindings(viewModel, document.getElementById("demo"));});

Important: Call the ko.applyBindings method only after setting a page locale.

For a more detailed description, refer to the following help topic:

This example illustrate how to bind the MVC GridView Extension with the standard in-memory data sources:

- The ADO.NET DataTable - DataTableDataBinding View / DataTableDataBindingPartial Partial View;

- The Typed List (List<T>) - TypedListDataBinding View / TypedListDataBindingPartial Partial View.

The GridView's definition contains:

- Set of Data Columns whose values are retrieved from the underlying datasource (the /*Data-Bound Columns*/ section);

- A single Unbound Column (the /*Unbound Columns*/ section) whose values are computed based on the bound columns' values (the /*Unbound Column Calculating*/ section).

Both data sources (Models) have the same set of fields. These Models are defined within the /Models/Model code file.

See Also:
E3983: GridView - How to edit in memory data source
E3998: GridView - How to specify a custom EditForm Template

Scenario

Orders, articles or other business entities often require that you have user-friendly Id or Code fields that end-users can memorize and use during phone conversations. They are usually sequential, but some gaps can be allowed as well (e.g., when an order is deleted). Refer to this StackOverFlow thread for more information on this common scenario, and a possible implementation.

Steps to implement

1. Add a new business class to your platform-agnostic module, and  call the static DevExpress.Persistent.BaseImpl.DistributedIdGeneratorHelper.Generate method from the AfterConstruction, OnSaving or other appropriate places within your persistent class or even Controller as shown in the Solution2.Module\BusinessObjects\Order.xx file. Depending on your business requirements, you can implement a readonly persistent or editable property where the generated value will be stored as well as check various conditions before generating the next sequence (e.g., string.IsNullOrEmpty(currentSequenceProperty) - to avoid double assignments, Session.IsNewObject(this) - to check whether the object is new, !(Session is NestedUnitOfWork) - to check whether the object is being saved to the database and not to the parent session, security system checks as per this blog post, etc.)

2. Build your platform-agnostic project and double-click on the Solution2.Module\Module.xx file to invoke the Module Designer;

3. Refer to the Exported Types section within the designer and expand the Referenced Assemblies | DevExpress.Persistent.BaseImpl node;

4. Select and press the space bar on the OidGenerator node to include this persistent type into the business model of your module:
Image may be NSFW.
Clik here to view.

IMPORTANT NOTES
1. The DistributedIdGeneratorHelper class demonstrated in this solution creates the IDGeneratorTable table to store the information about the last sequential number of a type. You can learn more on how this works from its source code at "C:\Program Files (x86)\DevExpress 1X.X\Components\Sources\DevExpress.Persistent\DevExpress.Persistent.BaseImpl\IDGenerator.cs".
Although this particular solution is simpler to implement and maintain (as it uses built-in XAF classes) than the How to generate and assign a sequential number for a business object within a database transaction, while being a part of a successful saving process (XAF) example, it is pretty safe and should also work in the most typical business scenarios (except for the middle-tier Application Server scenario, because the Session.DataLayer property is not initialized in this case).
2. If you have validation rules for your business class, the OnSaving method (and thus the sequence generation) is called only after all validation is passed. However, in rare cases, if a database related error is thrown during the first save and then the form is re-saved, the OnSaving method may be called again and a new sequence can be generated. This may lead to gaps in sequential numbers, which is not always allowed by business requirements (e.g., government regulations). To avoid this, you can use a more complicated solution from the How to generate and assign a sequential number for a business object within a database transaction, while being a part of a successful saving process (XAF) example or implement a database-level solution to handle such situations (e.g., using triggers).

3. You can find functional EasyTest scripts for this scenario in the Solution2.Module\FunctionalTests\E4904.ets file.

This example demonstrates how to create a GridControl descendant with horizontally oriented columns.

To use it, simply add the VerticalGridControl.xaml and VerticalGridControl.xaml.cs files in your project.

In addition, this example demonstrates how to customize grid cells using data templates.

To localize DevExtreme widgets, do the following:

- Link required dictionaries as described in the following help topic:
Link Dictionaries

Note that the order of references is important.

- Reference the DevExtreme localization script:
Use Predefined Dictionaries 

- Initialize your application after setting the locale:

[JavaScript]
$.when(...).then(

    Globalize.load).then(function(){..
    Globalize.locale('de');

    angular.bootstrap(document, ['dxApp']);});

Important: Call the angular.bootstrap method only after setting a page locale.

For a more detailed description, refer to the following help topic: