4 Replies Latest reply on Jul 19, 2013 9:51 AM by phanh

    Delete record in separation model

    phanh

      Our volunteer database allows users to cancel during the application process. If cancel, the record will get delete. Previous, this task is accomplished by the Delete Record/Request command. With the separation model, when this script runs, we receive an error "Your access priviledges do not allow you to perform this action." We even allow delete records for the volunteer account but it still doesn't fix the issue. Is there something else that we need to adjust?

      Also, when volunteers cancel the application, that current records removed and not show up in background check screen. With the separation model, the record is commited and shows in the background check screen (we think the delete command didn't execute). Do we need to create a temp/utility table (records) to hold the data temporally and commit at the end of the application process?

       

      Thank you in advance for the advices.

        • 1. Re: Delete record in separation model
          PSI

          You need to pass the same account privileges to the data file for that user.

           

           

           

          John Morina

           

          Pueblo Systems, Inc.

           

          CCQ-FM Inc.

           

          O: 631.549.0969

           

          C: 516.443.0966

           

          john@pueblo-systems.com

          • 2. Re: Delete record in separation model
            keywords

            Do we need to create a temp/utility table (records) to hold the data temporally and commit at the end of the application process?

             

            It does sound to me like this could be a case for using this approach. It works very well when you need to maintain tight control of the entry process.

            • 3. Re: Delete record in separation model

              Hi,

               

              With separation, all scripting should still take place in the UI (create layout based upon that data's table occurrence in your graph).  You can change the layout ( Layouts > Layout Setup ) and uncheck 'Save Record Changes Automatically'.  When asked, the User can say NO which reverts the record (and since it is new, it will not create it at all).

               

              You can also place unspecified button or web viewer over your layout which stops record commit.  Then place a SAVE button on the layout.  When new record is created, save script would commit or issue a Revert Record/Request[] as needed.

               

              Depending upon the data-entry layout itself, one technique or another would work best.  If portals are involved, i.e., they create a new parent record and also add kids with 'Allow Creation' on a portal, prohibiting commit (and allowing Revert) will also revert changes to the kids although a transactional model (search google for 'Todd Geist Transactional') offers maximum protection in situations where the parent's total is depending upon the sum of kids and time-critical such as posting month-end for invoicing.

               

              Overall, you can allow creation but either use layout setting or button to control if/when commit takes place.  If you would like further clarification on anything mentioned, please let us know and we'll explain more thoroughly. 

              • 4. Re: Delete record in separation model
                phanh

                Thank you, keywords and LaRetta

                 

                We probably will go with the utility table and commit all the data during the last step. The volunteers will not have to worry about saving the data constantly throughout the process.