I get the exact same result using migrator. Keep getting the "unique index" error.
Also, whenever I export to a def file...it exports both the original and the overlay form automatically. Are you saying that on a first update I should migrate\import both the original and the overlay...but then after only migrate\import the overlay?? Bruce -----Original Message----- >From: strauss <[email protected]> >Sent: Aug 16, 2011 4:28 PM >To: [email protected] >Subject: Re: Abandoning Best Practice Mode Overlay Feature > >I have had much better luck using migrator to move fields in form overlays. >Getting the initial overlay moved usually requires migrating BOTH the origin >and the overlay (since the origin now says it is "overlaid") - same thing when >you overlay a piece of workflow - migrate the overlay and the origin together >first; after that, you can migrate subsequent changes of just the overlay. > >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:[email protected]] On Behalf Of Bruce Sisk >Sent: Tuesday, August 16, 2011 2:08 PM >To: [email protected] >Subject: Abandoning Best Practice Mode Overlay Feature > >Good afternoon, > >I have been trying earnestly to use the new 7.6.04 Best Practice mode for >development but I have to say that I am at the point of wanting to abandon it >altogether. Has any one else come to the same conclusion or is everyone either >figuring it out or rather abandoning any idea of customizations? > >Here is my specific issue... > >I added a new field to the CTM:People form on my dev server. I did all of the >overlay stuff that I am aware of having to do...created form, view, panel >field and panel holder overlays. I placed the field in a tab on a panel holder >field. I created the field and eveything was beautiful. > >I then proceeded to export the form to a def file using Dev Studio and >imported it into production server which had no changes made to it at all. And >the nightmare begins!! > >I get an error "The value(s) for this entry violate a unique index..." along >with a new view of the CTM:People form...with many fields now no longer in the >default view or any view. I tried to back out of this by deleting the overlays >and the field. The problem now is that while everything seems to be back to >its pre import state in production, the field is still showing as a column in >the underlying database T table. It is NOT in the fields table...or the >view...or anywhere else except it is still a column in the table. > >I am very frustrated at this point. I hope that I am just not doing something >obvious and I can quickly adjust. Otherwise I will probably have to do the >hard work of getting to a stable state that I can then just stop trying to use >the overlay feature. > >ARS 7.6.04 >ITSM 7.6.04 >MS SQL 2008 >Midtier 7.6.04 > >Not on SP 1. > >Bruce Sisk > > > >________________________________________ >PeoplePC Online >A better way to Internet >http://www.peoplepc.com > >_______________________________________________________________________________ >UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >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" ________________________________________ PeoplePC Online A better way to Internet http://www.peoplepc.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
