Chris, are you suggesting: *B*ig *P*iece of *C*rap *U*tility? Jason
On Mon, May 2, 2011 at 8:59 AM, strauss <[email protected]> wrote: > Hah – I think I figured one of these out. I remembered that Matt - posting > on BMCDN – had told me that the BPCU strips all of the permissions from > custom fields when it moves them to the overlay layer (not documented). I > had forgotten that it ALSO strips all of the enumerations/attributes from > custom selection fields (also not documented). In order to restore your > custom fields after running BPCU, there has to be a new step PRIOR to Step > 11 where you compare every custom field to the originals on your 7.1 or > other pre-7.6.04 server that you are upgrading from, and you have to restore > all of the permissions to every field, AND all of the selection values. > Otherwise you get to the point where I am, with a reference server, staging > server, and pre-production server (where the latter lacks overlays and > custom fields entirely), and the reference server and staging server BOTH > have the custom fields MINUS their permissions and enumerations, so the > problem isn’t obvious in migrator when you are working through Step 14. I’m > having to go back and audit all of the custom fields between my 7.1 server > and the staging server, and manually correct each one, before I can migrate > them to the pre-production server. > > > > The BPCU really IS a complete piece of crap, isn’t it? > > > > Christopher Strauss, Ph.D. > Call Tracking Administration Manager > University of North Texas Computing & IT Center > http://itsm.unt.edu/ > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *strauss > *Sent:* Friday, April 29, 2011 2:45 PM > > *To:* [email protected] > *Subject:* Re: More FUN with 7.6.04 Form Overlays > > > > Both schemas – HPD:Help Desk, and there is no HPD:Help Desk__o - have the > same viewName and shViewName - HPD_Help_Desk and SH_HPD_Help_Desk, > respectively, and both resolve to T table 993. The only differences I see > in arschema between the two are: > > > > The overlay has an overlayProp of 2 (origin or base form has 1) and the > overlay has overlayGroup = 1 instead of NULL > > The overlay has a different schemaId and value in maxStatEnums (whatever > that is) > > The overlay has 26 more fields than the base form > > > > …it _*should*_ have 29 more fields, but there are three selection fields > that absolutely refuse to migrate from the staging server. They all throw > this error in migrator: > > > > *47*** > > *Errors results for Fields* > > *48*** > > Source Name > > Type > > Number > > Message > > *49*** > > 700000831 > > Migration Error > > 3700 > > Unable to create field : 700000831 > > *50*** > > 700000831 > > AR System Error > > 113 > > Name list parameter is empty > > > > I’m almost to the point where I re-create the custom fields that won’t > migrate by hand… > > > > 7.6.04 seems to pop new errors up daily. The “AR System Error 113 Name > list parameter is empty” is a favorite of Migrator. DevStudio is regaling > me with a continuous stream of “Required name parameter (or name field in a > parameter) is empty - Code 102” errors when I try to save the HPD:Help Desk > form on the staging server. This is after every successful save, after it > has created a bizarre Custom Audit form (with no name) at the top of the > Forms list. If you close the form without saving (your changes were > committed to the db), and reload the forms list it goes away, and then you > get one more edit and save in before doing it all again. > > > > This _*could*_ be construed as Friday humor, but I haven’t been laughing. > > > > Christopher Strauss, Ph.D. > Call Tracking Administration Manager > University of North Texas Computing & IT Center > http://itsm.unt.edu/ > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *LJ LongWing > *Sent:* Friday, April 29, 2011 12:20 PM > *To:* [email protected] > *Subject:* Re: More FUN with 7.6.04 Form Overlays > > > > ** > > Chris, > > I don’t run OOTB, so I can’t look specifically…but if you check in > arschema, there is a column that defines the ‘view’ that is created for the > T table. Is the view for the overlay different than the view for the base > object? If it is, see if you can query out of the alternate view name > properly….. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *strauss > *Sent:* Friday, April 29, 2011 10:48 AM > *To:* [email protected] > *Subject:* More FUN with 7.6.04 Form Overlays > > > > Here’s one for you. I was poking around in the Delta Data Migration > directories this morning, and found the sql scripts for counting records in > forms for each of the applications. Some of them have more errors than > correct lines, but that can be fixed; maybe the form names are instantiated > differently on other SQL systems (maybe they were created against oracle?), > but they were dead wrong for SQL Server 2008 (many form names too long and > therefore unrecognized). Also, a lot of the form names were invalid because > they were missing underscores – I’m not sure how anyone could have compiled > these scripts without ever testing them. If this is what the DDM uses to > run queries, there is no chance of it ever working correctly. > > > > Anyway, I tried to run a select statement in SQL for a custom integer field > on my HPD:Help Desk form to see if it has negative number entries that need > to be reset to “0” (see DDM doc pg 19), and found that I could not select > that field because it exists only in the overlay. In fact, you cannot > select ANY of your custom fields from HPD_Help_Desk, and there is no > HPD_Help_Desk__o in the form list, so I wonder where you can go in SQL to > query the overlays. HPD:Help Desk__o exists in arschema table with its own > schemaId, but it has no T or H tables etc., the custom field columns are > part of the T table for HPD:Help Desk itself. > > > > Select Outage_Duration from HPD_Help_Desk WHERE Outage_Duration < 0 > > …is not a valid command – Outage_Duration is not recognized by SQL Server > as a valid column in the HPD_Help_Desk table > > > > If I try querying the T table directly, that works: > > Select [C940000006] from dbo.T993 WHERE [C940000006] < 0 > > > > So are custom fields in form overlays undefined in the SQL Server > namespace?? > > > > Christopher Strauss, Ph.D. > Call Tracking Administration Manager > University of North Texas Computing & IT Center > http://itsm.unt.edu/ > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
