Incorrect code written by another developer, to create People Permission Group records for new users that were added from an external data source (LDAP) got the information in the People Permission Groups form out of sync with the Group List information on the User form. The bad code modified existing PPG records instead of adding a row when a new user was created because of a bad push field if condition..
I have fixed the workflow that caused that, but now have to repair the damage – I now have to fix the damage done to the data that went bad as a result of this (which will be the more fun part – I’m hoping).. Restoring the DB might be your intuitive suggestion, but this unfortunately isn’t an option. This bug in the custom workflow went unnoticed for several months after the bad code was implemented, and the oldest available backup, is very recent – in comparison to when the bad code went live.. I was toying around with the idea to develop a SQL code whose results would create a CSV file required for the PPG form, based on the contents of group_list in the user_x view.. I want to be able to write a good SQL that would generate this data, based on the correct conditions for records that need to exist on the PPG form.. If I am able to do this, I can truncate the data existing in the PPG form (and its H table), and import the CSV file to fix the data. I wanted to know *ALL* the conditions & rules under which a PPG record is created. I think I do know the answer, but because I am attempting to repair foundation data gone bad, I do not want to be missing any possibilities.. Cheers Joe _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
