Okay, maybe not... NTE:SYS-Define NT Events is schemaId 606 BPCU created NTE:SYS-Define NT Events__o as schemaId 2032 because I added some notifications and that required additional attributes in the Notification Event field.
NTE:SYS-Define NT Events 7.0.03 had 95 records and a nextId of 118 NTE:SYS-Define NT Events__o has a nextId of 118 - picked up when it was created by BPCU After the upgrade to 7.6.04... NTE:SYS-Define NT Events 7.6.04 has 151 records and a nextId of 3356 (Next-ID-Block-Size: 100 during upgrade) NTE:SYS-Define NT Events__o remains at a nextId of 118 ...so they do NOT stay in sync. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of strauss Sent: Thursday, April 21, 2011 1:47 PM To: arslist@ARSLIST.ORG Subject: ARS 7.6.04 Form Overlays - nextId increments Observations: On my upgraded 7.6.04 system, there are now TWO schemas: HPD:Help Desk (schemaId 993) HPD:Help Desk__o (schemaId 2052) There are still the usual T, H, and B tables for 993, but NONE defined for 2052. On first glance, schemaId 2052 appears to exist ONLY as an entry in the arschema table. Since it does not have a T-table, the actual data for my custom fields must still be stored in T993, correct? Both tables have the same nextId - 59161. Which one do I set to 100000 if I want to create test tickets in the overlaid system? Both? Will they increment together? If not, what happens if you ever decide to delete your form overlay and go back to the origin object... will the nextId value be out of sync? Inquiring minds want to know... No I haven't tested yet - I have to get to a point where I can easily roll the db back after I (potentially) screw it all up. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/
