Hi Andrzej,

For your experience with a cache, I have informed our development teams for this issue.

Regarding to your question about ExecuteValidateRow, your sample in this thread show me that you used ExecuteValidateRow event. Is it still not trigger as you expect ?

Regards.
Riendy

Hi Riendy,

if I don't add entity to EntityManager like on example below:

private void ExecutePrepareNewRow(object parameter)
        {
            // It's possible to initialize the new row with default values
            // Example:
            // product.ProductName = "New Product";
            this.NewItem = this.EditableProductsSource.Create() as T;
            //this.EditableProductsSource.Insert(this.NewItem);
        }

only RejectRowCommand ( ExecuteRejectRow method) is executed.

I expect it should be extecuted:  ValidateRowCommand, InsertRowCommand too.

You can try it  (file: EditableGridViewModelGenericBase.cs)

Kind regards

Andrzej

Hi Andrzej,

EntityManager is an item from devforce. The process that you did in UXGrid would be save on entityManager before you save or cancel the processes (save all changes/reject all changes) to dataSource. In simply, we can call it client caching. That is why batch update not available in all data providers such as WCF RIA service.

In brief, you have to add NewItem to EntityManager, because you use DevForce service.

For your other experience with our template, if you want to clear the processes that haven't click save all changes button, you may add following code in you xaml, ie :

ProductRepository repository = this.DataSource as ProductRepository;
Repository.Context.Clear();

When this code applied, the "cache" will be clear when the xaml opened.

Please let me know if it is not answered yet.

Thank you.
Riendy

Hi Riendy,

Anyway ..

I would imagine the following process:

1. user click on new row:

  a. ExecutePrepareNewRow is raising - in code we create new object(entity) and set some default value

2. user add new row to list

  a. ExecuteValidateRow is raising - in code we validate object (entity), if 'ok' than insert it into EntityManager

  b. ExecuteInsertRow is raising

3. user click Save and all new added entity are saved via DevForce to DB

UXGrid offer me another life cycle:

when user click new row I have to add new entity to EntityManager (in ExecutePrepareNewRow) - I don't do that, because there is no my accept at this moment. 

Have you ever tried some kind of magic:

1. go to Product

2. click on new row and write ProductName="abc" and Category="Beverages"

3. next click on Home

4. and back again to Product -what you see : new added row 

Why I have to take care to clear cache or permanently use sandbox with new instance of EntityManager

I think it's not good practic which required more control.

Kind Regards

Andrzej

BTW

Sandbox is very good practic

Hi Andrzej,

I meant, if you have to clear the cache, but it is not suggested because it same as remove some DevForce service. The batch update on this state should be enabled. Unfortunately in the fact, the batch update is disabled. Our development team has been known this issue and I ensure they will fix it as soon as possible.

Regarding to your scenario, I'm currently still investigating to provide a solution for you.

Regards.
Riendy