I am attempting to edit/save (aka update) selected BO's represented on a grid. Here is the code that I am using to accomplish this seemingly easy task:







The result of this code is that only the first and last record are updated. All other selected parts in between are ignored. Each part number shows up in the WaitWindow as I cycle through the selected records; however, only the first and last records are actually persisted to the database.







Any ideas?



Thanks,

Bill

OK, there can be a number of things going on here. First, you are using a grid and trying to seek within grid events...thins can get hairy because the grid ultimately wants control. the ONLY way this can happen...seriously...the ONLY way is if the BO is navigated to these records. So one of the following this is going on:



1. The grid is navigating to these records when when getting the values.

2. You have a sort or filter applied (or the grid is applying one)

3. The planets are beginning to align for a total eclipse!



Possible Resolutions or Debugging Ideas:



1. Remove any filters and/or sorts

2. Put a break point in the navigating event of the BO and then look at the call stack to see what is navigating the BO.

3. USE A LISTVIEW In this particular screen shot, I see no reason for the grid. Grids are fat and have a ton of overhead. When just displaying row elements that are maintained OUTSIDE of the grid, you are asking for trouble. Just my 2 cents!

That's it!!!



I'll start by replacing the grid with a list. We'll see what happens after that. Thanks (as always) for the tip!



Bill

Ok. The ListView displays the data from a query within its own assigned business object. I can even copy the data from the form's business object after the current data table is refilled. That work nicely to pick up the browse dialog's search results. But I need the list to directly reflect the business object on the form and to navigate the business object when the pointer changes on the ListView. I do not see how to get these two items to work in tandem. Also, even though I have set the ListView to multi-select, only one row at a time can be selected.

AutoNavigateToSelectedRecord



Setting this to true did the trick of synchronizing the list to the BO.



Now, I just need to get the multi-select feature to work.

You will have to set the MultiSelect property to true in code. It is overwritten by the default class (to resolve other issues fought in the past). So after the OnLoad, set this and you should be good.

Yepper...that was the ticket.



So far, we have replaced that fat grid with a thin list. The list is playing nicely with the BO on the form and I can multi-select the items on the list.



Now, when I rifle through the selected items and try to seek to that record...the edit/save routine does not work. The wait window displays the selected parts (see code above), but does not actually persist my change.



Still at square one. But, I did learn some things.

What does your code look like now? Also, why are you calling edit? As you as you make a change the BO will become dirty. So there is really no need to place the BO in edit mode.

Here's the code...I did take out the Edit(). I am now testing without it. I'll let you know if that changes anything.

If I select the first four in the list...only the first one is persisted.

If I pick the second through the fourth...only the second one (first in my selected items) is persisted.



I have got to take off. I'll try to check in later today to see if I can try working on this again.

First, I would use a foreach. I would do something more like this:

Hi Bill,



Adding to Trent's reply, I have a this suggestion:



1- I use the ListView extensively, and in your case, I would use the ListView.Checked property instead of MultiSelect, with this you will have better control on what records are currently checked since the list view has a collection for it, and it will be easier for the End User to just click the box or double click the record to check it. (See attached screenshoot)







As you can see, in my case I am deleting the current row, but you'll get the idea, and of course my code is in VB

Edhy Rijo

Hi Edhy,



I did try using the checked property; however, the user loses the range select (click, shift-click) option. The user would prefer to do that than click 30+ checkboxes.



Trent, I tried that code, but I am getting the same results. Only the first record is getting persisted; however, all selected items are being seeked because the part number shows up in the wait window perfectly.



I am tackling this again today. After a really nice weekend, hopefully, I'll be able to conquer this pesky little issue.



Thanks!!

Ling

Then there has to be something either set within your BO or some other logic moving the CurrentRowIndex because I have done this repeatedly. You are welcome to supply a sample, but I know that this will work as it is a common piece of logic.

There was other logic resetting CheckButton. I discovered that and replaced the CheckButtons with a RadioGroup (a little cleaner). I was able to remove all of my extra fancy code to manage the checkbuttons and now the form works as expected. It is clean and fast! Thanks for all the help!!



Have a great day!

Bill

Glad you got to the bottom of it!