Editable field in Grid with problems

yuri.rj

After update to the latest version, my grid stopped working correctly
(Simple grid, grouped by one attribute, with editable date fields).
Every time i click on an editable date field with a blank value, it let's me edit the value, but shows the value from another record.... And when i finish updating, it updates another record that i haven't selected....
I think it's a huge bug....
My clients are updating the wrong record... some of the records are messed up now....

aware_support

There is no bug. If there was Aware IM would have been unusable. And it is used by many and noone reported this. Most probably you or your customers haven't refreshed their browser to pick up the latest Javascript file from the new installation.

yuri.rj

Support,

This sentence seems a little bit arrogant and it should not be a way of talking to a customer, but i'll ignore that.

So anyway... i did this...i tried on a machine that have NEVER accessed the application.
And the BUG still happens.

By your sentence, i really believe that you doubt my words, so i made a video to proof what i'm saying(I don't need to say that i think outrageous that you didn't even try to reproduce the problem, but once more i'll ignore that).

Indeed, maybe i have not configured the application the right way, and help would be appreciated.

here goes the link to the video:
http://youtu.be/-SblBGOa3rc

Explaining the video(i don't know how to put subtitles)
1 - 0:10s - Tried to edit a date from a record on row number 4. (You may see that ROW NUMBERS ARE MESSED UP)
2 - 0:10s - On the editable field, showed up a value from row 6.
3 - 0:26s - After i changed the value, row 4 BECAME row 6 (!!!!!!!!!!!!!!!!!!!!!!!)
4 - 0:52s - Saved changes on the grid
5 - 1:00s - Row 6 had its value changed
6 - 1:10s - Tried to edit value of row 6 to fix all SHIT that happened
7 - 1:12s - When i clicked outside the editable field(without changed the value), the record DISAPPEARD from the screen(its not deleted)

I think you may consider take a look on this NON existing bug even if i'm the first customer to complaint.

Regards

tford

Support has long demonstrated a willingness to review & fix well documented issues / bugs.

The best way to isolate & document a bug for support and get their prompt action is to create a mini BSV .. one that is created simply to demonstrate the issue at hand. If you send the BSV along with specific instructions on how to duplicate the unexpected behavior to support, they have a track record of addressing them promptly.

This approach ensures that no miscellaneous rules, etc are causing the unexpected behavior in the BSV.

yuri.rj

Tom,

I really think that what I'm doing here is something helpful for them. It's not my job to test the tool... It should work correctly PERIOD! I was surprised to be treated like that, when I was warning about something that can really cause some damage in people who is using an application that has these components. It's something that is not too visible to the end user... They can realize the problem after mess up the data.

But I really appreciate your advice.
Next time I'll try this way and try to make things easier for them.

Cheers

aware_support

Our apologies if the previous response sounded arrogant. It was't our intention at all.

But please try to understand our position here:

We get a large of number of questions/issues that turn out to be user mistakes. We cannot afford to address every single one of them for free.
If you have an issue that you think should be urgently looked at - please sign up for one of our support plans or pay for the support ticket. This is irrespective of whether you think it's a bug or not.
Please report the problems as Tom suggested - this will make our life and consequently your life a lot easier. Please also see the sticky thread on this forum that explains how to report problems properly.
Your video doesn't help at all. We have absolutely no doubt that you are not lying (noone is) and that you are experiencing some kind of a problem. But we cannot do anything about this problem from your video., because we cannot reproduce it. For all we know it could be down to a mistake somewhere in your application. Or it could be a genuine bug.

Which is why please look at points 2 and 3 above and do the right thing. Your cooperation is highly appreciated.

aware_support

And also double check that you have no rules attached to the object that can change some other record