Joe,
People Permission Groups contains data NOT held in the User table (or anywhere else). Remember that you can have many equal permissions and people based on the other data in the record. See the structure of the table and see some of the records you do have. A push to People Permission Groups requires a value be pushed to a DO field to initiate the workflow to synchronise the User permissions groups value. This is more likely your situation. The fix is simply to add that to the push fields action. z1D Action = START Are you sure that you are missing the rows in this table and not the reverse? Generating missing rows in this table is non-trivial because of the missing data. Correcting the User Group Permissions based on the data in People Permission Groups is more realistic through still non-trivial without a Meta-Update script (available). Cheers Ben Chernys Senior Software Architect Description: logoSthInc-sm Canada / Deutschland Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: <mailto:Ben.Chernys_AT_softwaretoolhouse.com> Ben.Chernys_AT_softwaretoolhouse.com Web: <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com Check out Software Tool House's free Diary Editor and out Freebies Section for an ITSM 7.6.04 Forms and Fields spreadsheet. Meta-Update, our premium ARS Data tool, lets you automate your imports, migrations, in no time at all, without programming, without staging forms, without merge workflow. <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/ www.softwaretoolhouse.com From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: May-07-12 19:21 To: arslist@ARSLIST.ORG Subject: CTM:People Permission Groups form related question.. ** 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 _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
<<image003.jpg>>
smime.p7s
Description: S/MIME cryptographic signature
