1 Reply Latest reply on Aug 4, 2015 5:14 AM by SteveMartino

    Not commiting data entry to protect original data

    JeongwungJeong

      Title

      Not commiting data entry to protect original data

      Post

      Hello Experts

      I made two layouts with same table. One is for "original" and the other layout is for "editing".

      To protect original data fields I unselected "browse Mode" at the original layout. And I put an "edit" button to go "editing" layout which has selected "Browse Mode" so that I can edit the data only in "Editing" layout.

      But the problem is that the data I changed in "Editing" layout is automatically committed and the data in  "original" layout is changed at the same.

      It sounds natural because the fields are eventually one even though the layout is different.

      I wonder if there is other way not to commit the data in "editing" layout not to change the original data in "original" layout?

      My plan is to put "save" and "cancel" buttons on the "Editing" layout. And the data entry committed only when I click "save" button. 

      To solve this problem I make another table for editing and transfer data to the original table. but this is very complicate and time consuming to make other field for edit and develop the script.

      I am looking for simpler way. Any good Idea??  Please help.

      Thanks

      JW

        • 1. Re: Not commiting data entry to protect original data
          SteveMartino

          This is a fairly standard practice.  You make a layout where all the fields are mimicked as global fields.  The save button then runs a script that takes the values in the global fields and enters/edits them in the correct fields in the original layout, commits the changes and clears the globals.  Another option is to employ an audit table where you can track changes and roll them back if need be.  I think there are a few 3rd parties plug ins that do this.