• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Value of a field before it was changed? local data edit grid

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Value of a field before it was changed? local data edit grid

    Hello Team,
    I'm using the edit grid with local data. It's working great. There is one thing I'm looking to do and I'm not sure if it's possible. When my user changes a value in a cell in my edit grid, with cell editing, is there a way for the grid validation program, or any program really, to store what the value was before the change? Pretty much what I'm trying to accomplish is preventing an update/refresh routine if the value is not changed. Right now, if a user clicks a cell, and doesn't change the value, the front end is still sending that field as changed to the backend. I know I could do this if the edit grid was not using local data, but I don't want to switch it back. I like the UX with the local data.
    Thanks.

  • #2
    Are you saying that the edit grid validation program is running each time that a user exits a cell regardless if the cell value was changed or not?

    Comment


    • #3
      Correct, it not validating that anything changes, it runs as soon as the user exits the cell. When looking at the logs, the first time I'm in the grid select the cell, and then press tab to exit the cell, the isChaged value stays false. If I do change the value, isChange switches to true. Then if I go back to that cell, and tab out of it without changing it, isChanged stays true. I'm wondering if isChaged only knows if a value has been changed from what it was originally set to.

      Comment


      • #4
        This sounds like a bug on our end. Will dig in further and post back later today with an update.

        Comment


        • #5
          This will be fixed in the next update.

          Comment

          Working...
          X