Sorry to bump, but was really hoping to get a response to this..

Thanks

Hello Matt,

Thank you for your post. I have been looking into it and I can suggest you see the sample in the Samples Browser under Persistence Framework / Organization / Persist xamGrid Settings section, where there is a sample showing how to save settings from one grid and apply them to another one. Please let me know if this helps you or you need further assistance on this matter.

Looking forward for your reply.

Thanks for the reply, however the snippet here:

        private void btnSaveState_Click(object sender, RoutedEventArgs e)
        {
            // Saves all sourceDataGrid properties
            // except Rows, ActiveCell, SelectedCells, SelectedRows (ignored by default)
            MemoryStream memoryStream = PersistenceManager.Save(sourceDataGrid);

            memoryStream.Position = 0;

            // Loads all saved properties from sourceDataGrid to targetDataGrid
            PersistenceManager.Load(targetDataGrid, memoryStream);

Only works on the SAME machine in the same instance of the application run...

I am persisting settings in a Database so that they are saved across sessions. This works perfectly except when settings are shared between machines.

To clarify:

User 1 saves Grid Settings 1 in the DB. Each time he loads the grid, it works Perfectly.

User 2 loads up a Grid, and applies Grid Settings 1 from the DB, and the grid goes completely blank and cannot be reset.

Thanks for the assistance,

Matt.

Another way of thinking about it is this:

In a Database there is a Persistence setting for a XamGrid. Every user has access to this, and on loading up the application, this grid settings are queried and applied to the grid.

The problem, is that the settings will only work for the 1 user that actually saved the setting from their grid... no one else. (hence me thinking it must be some kind of guid or identifier from somewhere... )

I appreciate this is a non-trivial issue to replicate or offer a coded solution to, but I really would appreciate the help..

Thanks again,

Matt.

Hello Matt,

There isn't any unique number that is saved in the file, but if you send me an isolated sample project, where this is reproduced or at least a code snippet of your XamGRid definition and the code that loads the data and save/load the settings I would be able to investifate this further.

Looking forward for your reply.

Excellent thanks!

I really hope this is picked up as the persistence stuff is really cool and my users love it when it works ;)

Hello Matt,

After some research Load XamGrid if persist fail has been determine as a new Product Idea.  I have sent your Product Idea directly to our product management team.  Our product team chooses new Product Ideas for development based on popular feedback from our customer base.  Infragistics continues to monitor application development for all of our products, so as trends appear in requested ideas, we can plan accordingly.

We value your input, and our philosophy is to enhance our toolset based on customer feedback.  If your idea is chosen for development, you will be notified at that time.  Your reference number for this Product Idea is PI13050081

If you would like to follow up on your Product Idea at a later point, you may contact Developer Support management via email.  Please include the reference number of your Product Idea in the subject and body of your email message.  You can reach Developer Support management through the following email address:  dsmanager@infragistics.com

Hi There!

In trying to create a scenario where I could test your suggestion, I kind of stumbled across the answer...

My Grid settings are saving the entire layout.. Columns and all.. and it seems that between releases, or even between sessions, depending on whether use has gotten the latest verison of the Silverlight Client, the Grid Columns may be different.

This makes total sense now. However, it leaves me with a huge problem.

Our grid is the central driving data component of our application. And currently, there are 3 of them, and this will increase in the future, and the ability to store Grid Settings, and apply them without things exploding is a requirement.

My assumption was that the resulting XML of the Persistence settings would only work on the Columns that were Defined AND present, not blow up if a column appeared that was not defined, or defined but no longer present... Can I consider this a bug?

At least, is there a way to detect if the settings being applied do not match up with the Grid in the application?

That way, I could fail the grid settings application early, and give a message saying that they need to update the grid settings....

Or alternatively, is there a way to remove the resulting grid white out if this DOES happen...

Eagerly awaiting a reply!

Many thanks

Hello Matt,

I am looking forward to hear from you.