We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Grouping by Related fields

Thread ID:

Created:

Updated:

Platform:

Replies:

56464 Feb 15,2007 08:21 AM Feb 22,2007 02:06 PM Windows Forms 3
loading
Tags: Grouping
Sergey Tikhomirov
Asked On February 15, 2007 08:21 AM

Hi,

We continue our investigations with Essential Grouping.

In attachment example of workflow that for our opinion works incorrect.
Press "Make Test" button for execute this workflow.
In comments in this function we've wrote expected result.

Below you can find description of this workflow step by step

1. Create two BindingLists of some objects.
2. Add relation (RelationKind.ForeignKeyReference) between these two lists.
3. Add Grouping Column that works using this relation with
m_oEngine.TableDescriptor.GroupedColumns.Add("OurCustomRelation.AuxilaryName");
4. Expand all records by calling
m_oEngine.Table.ExpandAllRecords();
5. Iterate through m_oEngine.Table.NestedDisplayElements collection, everything is fine so far.
6. Change the value of some property for one of the elements in child collection.
7. Send ListChange event from child list.
8. We expect that data will be automatically regrouped.
9. When we iterate one more time through m_oEngine.Table.NestedDisplayElements we see old result, for us this is not correct.
10. If we send ListChange event on parent list all works fine, but it can be difficult sometimes to send such event.

We use Syncfusion 4.4.0.51 and Visual Studio 2005

Best regards,
Sergey Tikhomirov
Senior Developer



CollectionWithRelatedMasterGrouping0.zip

Administrator [Syncfusion]
Replied On February 15, 2007 10:58 AM

Hi Sergey,

Before calculating summary count in a Auxilary List Change, try setting the Table.TableDirty to true. Here is a code snippet.

ChangeAuxilaryData(1, "16");
m_oEngine.Table.SummariesDirty = true;
m_oEngine.Table.TableDirty = true;

iCountAfterAuxilaryListChange = CalculateNestedSummaryCount();

Please refer to the attached sample for modification.
CollectionWithRelatedMasterGrouping.zip

Thanks for you interest in Syncfusion Product.

Best regards,
Haneef

Sergey Tikhomirov
Replied On February 19, 2007 10:14 AM

Hi,

We've looked your solution.

It's really solve problem with group data.

But we've tested it on huge portion of data.
And we encountered with performance problem.
We understand that first time group calculations should takes a lot of time.
But in our workflow after changing of Auxilary Data calculation of new groups needs a lot of time too. And this time is greater than first calculation time. And this looks confusing for us.

In attach you can find the solution with our test.
Press Make Test button and look in the Output window our performance logging.

Can you provide any solution avoiding this problems?

Best Regards,
Sergey Tihomirov


CollectionWithRelatedMasterGrouping_20070217.zip

Administrator [Syncfusion]
Replied On February 22, 2007 02:06 PM

Hi Sergey,

Please refer this.
http://www.syncfusion.com/support/forums/message.aspx?&MessageID=56915

Best regards,
Haneef

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;