Database Changes

Just curious if it's an acceptable practice to modify the ESC database?  Specifically, I would like to add a Time Stamp field to the PO table to record the date the PO was imported into an invoice.  This way, I can tell if the PO costs have been recorded against a PO to show true GP.

 

Thank you

0

Comments

5 comments
  • Hey JJ!

    You are absolutely able to do that if you know how.

    While our ESC support staff will always go above and beyond to help any way they can; keep in mind they are not trained in modifications to ESC databases and may be unable to assist with an issue directly related to a modification to your database. But we'll certainly do our best to try!

    Also, make sure you take a backup of your database BEFORE you attempt the modification. This will ensure that if there's even an issue, even if it's unforeseen for quite some time, that you'll have a functional copy of your database before that modification took place.

    0
    Comment actions Permalink
  • Something to be mindful of here and the ESC support can speak to this, is when you make modifications to the ESC database those changes can be potentially overwritten by an update put out by the ESC team. 

    A potential better way to accomplish this would be to create auditing triggers on the ESC table you would like so that every time there is a change to that table the trigger would write to a different database (you could call it PO_Timestamp) and have it insert that line of information into it. This way you can write a query that joins your PO_Timestamp table to the ESC table and get a comprehensive picture of the activity of the POs. You could also have a more in-depth view as you can allow it to timestamp each change, this way to are able to see every time something changed on that table, not just a single timestamp with that one PO record.

    Just some thoughts...Also would love to hear from ESC if their updates would remove a value like what JJ is asking for. 

    1
    Comment actions Permalink
  • That is a great idea...and updates wouldn't remove the new functionality since it's a separate database.

    0
    Comment actions Permalink
  • Just curious if any ESC peeps saw Luke's question about an update overwriting a audit trigger???

    0
    Comment actions Permalink
  • I am not a coder, but I can say that ESC updates do overwrite changes to the database. We solved that by having our programmer save his tables before installing the update and then re-installing them afterward. It didn't seem to be a problem after that.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post