This is a migrated thread and some comments may be shown as answers.

URGENT issue in editing hierarchical grid

21 Answers 202 Views

GridView

This is a migrated thread and some comments may be shown as answers.

Eyal Yaari asked on 03 Aug 2010, 03:37 PM

After creating a hierarchical bound grid with two levels(two different binding sources) for example, you exit Visual Studio 2008 and then go back in to change any of the properties of the columns in the child template(from within the design view) it will work fine, you can do a build, run it, and even see the changes in the designer.VB file. But then when you exit Visual Studio 2008 SP1 again and get back in again, the changes you made to the child template are gone! from that point on it accepts no updates or changes of any kind from the design view.

I also did a fresh install of Visual Studio 2008 as well as the Telerik install on my virgin laptop and created a new project. Same problem. the only controls I am using are the radribbonform and the radgridview within it. if you can't reproduce it for some reason I will attach the project

Please get back to me ASAP since this is very urgent. I can't continue. I'm at a dead-end unless you have some workaround that I can use.

Thanks, Eyal

21 Answers, 1 is accepted

answered on 06 Aug 2010, 03:48 PM

Hi Eyal Yaari,

The answer to your question can be found in the other ticket that you have submitted - 334652. Please, see our answer there for more information.

We kindly ask you to use just one support channel to contact us. Posting the same questions numerous times slows down our response times because we will need to review and address two or more tickets instead of one. Moreover support threads are handled according to license and time of posting, so if it is an urgent problem, we suggest you use a support ticket, which would be handled before a forum thread. Forums are treated with 72 hour response time, regardless of your licensing package.

Thank you for your understanding.

Regards,
Stefan
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

answered on 06 Aug 2010, 05:25 PM

I'm sorry but I thought that it was appropriate to post in the forum as well as open a trouble ticket. The reason is that I thought the forum is meant to share issues and experiences using the software with fellow users while the trouble ticket was meant to be directed only at the company's support staff. If I were to just open a trouble ticket with the company, then wouldn't the benefit of the answer be lost to all of the other users in the forum? maybe the correct way to do it is to mention in the forum post that a trouble ticket was also opened? either way, sorry for the confusion. I also posted a response to your response in the support ticket and will continue to just update the ticket and not the forum.

thanks

answered on 11 Aug 2010, 01:47 PM

Hi Eyal Yaari,

Sorry for the confusion - we were left with the impression that you needed urgent help, and this was the reason for the two posts, i.e. push us to reply faster. Again, sorry for the misunderstanding.

As a rule of thumb, if you need urgent assistance, support tickets are the way to go as they are reviewed with priority when compared to forum posts. Forum posts get a default of 72 hour response time, whereas tickets get either 24 or 48 hours, depending on your license.

In case you want to share something with other users, you can simply open a forum thread. The Forums also allow you to benefit from other users' experience and ideas on the discussed subject. In such cases there is no need to open a support ticket.

I hope you find this information helpful. In case you need any other assistance, do not hesitate to contact us.

Regards,
Stefan
the Telerik team

answered on 10 Nov 2010, 11:11 PM

I can definitely sympathize. I lost weeks of work struggling with that and other issues. The "fix" I was given was "don't use the property editor, but rather use code instead until we fix the bug". But I really didn't feel like coding everything so I did a bunch of different things and I'm not sure what actually did it. My guess is the top three things were: upgraded to their latest version, didn't use the smart tag for the grid, and probably most useful was deleting the grids and redoing them from scratch. I can't remember if I also reinstalled Visual Studio but if you can do it it couldn't hurt. I suspect it's less of an issue with Visual Studio since I tried it with a competitors grid software and all the features worked like a charm, not a single bug that I can see. so that's my experience for what it's worth.....

-- Eyal

answered on 10 Nov 2010, 11:43 PM

Thanks to both of you.

Emanuel: I'm using Visual Studio 2010 with an upgraded version of the grids (I upgraded from 2010.1.10.504 to 2010.2.10.914) and this behavior is new to me (I mean since the upgrade...). I will try the serialization procedure but after reading about it, I'm not sure if it will do what I need.

Eyal : I tried several things myself too.. I first thought it had something to do with the fact that I upgraded my controls to version 2010.2.10.914 with all the major changes... First none of the filters I had were correct so I had to redo them all, then also none of the child templates I had were working either. I had to redo them all and that's how it started to be problematic. I tried also to completely delete the grid but I still experience the issue even if I start from scratch.

It's really weird.. I can erase columns, change the header text, change the format strings everything is fine until I do something (I suppose...) that remove all the customization and bring back the columns like if I just added the datasource... It's really strange.

Again guys, thanks for your effort in helping me.

answered on 19 Nov 2010, 07:20 PM

Marc,

I just remembered the other useful piece of advice their tech support gave me. In addition to not using their property editor, take away/deactivate the property that auto generates the columns. When you first create the grid you can set it to true which I believe is the default, but after it populates the grid with the column names, set it to false so that every few days or so when you're program freaks out and decides to regenerate everything as it originally was, it leaves those grid columns alone. I remember that actually did the trick. Sorry that it slipped my mind when you first asked but you know how trauma is… Your brain erases all painful memories in self-defense:-)

As far as autosize, I killed that property from the get go since it slowed down the refresh and redraw considerably, especially in a hierarchical grid.

Hope that helps,

Eyal