Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
920
Grid update
posted

Hello. I've a binded UltraGrid with a few unbounded columns added like its say here. The grid is updated with a UltraGridRowEditTemplate. For that reason I've created the Band in the designer with the columns I'll use. The rest of the columns are hidden after assigning data source.

The problem is that when updating a row (or adding one) on the blur of any of the fields the editor lose its value. I can't understand why this is happening.

Why can this be happening?

Note: I've tried and this is not happening only when editing through the UltraGridRowEditTemplate.

Note 2: I've also noted that I've two fields in the editor that y can't edit. One of them it's because I've set CellActivation = NoEdit but in the other one I can't figure out why is this happening. Could this have anything to do with the other error? The read-only fields (both voluntary and unvoluntary) are of DataType = DateTime and bounded.

 

In the meanwhile I'll try to collect some more information. If anybody thinks that may have a clue but need specific information please ask me, I'd already spent hours trying to correct this behavior.

 

Thanks, Diego

Parents
No Data
Reply
  • 469350
    Offline posted

    Hi Diego,

    I'm afraid I don't understand what the problem is.

    dpaska90 said:
    The problem is that when updating a row (or adding one) on the blur of any of the fields the editor lose its value. I can't understand why this is happening.

    What's a blur?

    If you are unable to edit a field in the grid, then the most common reason for that is one of the following:

    • You are setting CellActivation on the column to something that does not allow editing.
    • The field is bound and the data source does not allow editing.

    It sounds like you are saying that you can edit the field, but then when you leave the cell, it's reverting back to the original value. I've never heard of that happening on a DateTime field. My best guess is that your data source is rejecting the new value for some reason.

     

Children