Instead of hardcoding, you can retrieve the viewname from ARSchema table during run time by adding a set fields action.
Thanks Mahesh On Wed, Apr 11, 2012 at 2:25 AM, Jose Huerta <[email protected]>wrote: > ** This last sentence is not 100% true. I agree with you with the > recommendation of pointing to views at direct SQL actions instead of T > tables. But, although it is very unlikely, it is not guaranteed that the > view name of the form won't change when migrating. If two form names > collide with the view name one of them will have the scheme number in the > name. > > El miércoles 11 de abril de 2012, Joe Martin D'Souza escribió: > > ** >> >> A very useful tip: >> >> Many of you may know this.. If you MUST write a Direct SQL, you NEVER >> should write SQL directly to T tables.. Instead write them against the view >> name.. for eg if you wanted to write one for the HPD:HelpDesk form whose >> table is lets say T654 do not write it to T654.. Describe HPD_HelpDesk and >> write it to that.. Then the upgrade would be seamless as the view name >> never changes.. >> >> You may want to consider a project where if you have Direct SQL’s to the >> T tables, convert them to address the view names.. >> >> Joe >> >> *From:* Susan Palmer >> *Sent:* Tuesday, April 10, 2012 7:57 PM >> *Newsgroups:* public.remedy.arsystem.general >> *To:* [email protected] >> *Subject:* Re: Transferring in-house 6.3 code to a 7.6.04 server >> >> ** We did an upgrade (mis-nomer) last year. After 3 months of trying to >> upgrade we ended up just creating new servers and export/importing >> objects. The biggest gotcha we ran into was when you import forms to the >> new database it changes the form ID (T236 became T450). Any sql statements >> included in workflow needed to be updated and external programs needed to >> be updated. >> >> There were other things and if you take the time to search archives I >> described them pretty extensively. >> >> Good luck!! >> >> Susan >> >> On Tue, Apr 10, 2012 at 11:05 AM, David M. Clark <[email protected]>wrote: >> >>> ** >>> >>> Folks,**** >>> >>> **** >>> >>> I am finally in the process of upgrading our 6.03.00 patch 017 >>> implementation to the latest offered. By “upgrade” I mean a transfer >>> between old and new servers, not on the same server. The revs are >>> apparently too far apart to use Migrator to transfer code between, so I >>> will be using a 7.1 server as an intermediate transfer point. Migrator 7.1 >>> from the 6.3 box to the 7.1 box, then the latest Migrator from the 7.1 box >>> to the 7.6.04 box. I’ll also be using Export/Import tools as needed. Note >>> that no BMC Remedy applications are involved here, though I will be loading >>> ITSM later. My concern now is only with in-house developed code created >>> under or compatible with version 6.3. Solaris and Oracle on both sides. >>> **** >>> >>> **** >>> >>> Anyone ever done this or have any suggestions as to problems that I may >>> encounter?**** >>> >>> **** >>> >>> Thanks,**** >>> >>> **** >>> >>> -David >>> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > -- > > Jose M. Huerta > Project Manager** > > Movil: 661 665 088 > > Telf.: 971 75 03 24**** > > Fax: 971 75 07 94**** > > <http://www.sm2baleares.es/>**** > > SM2 Baleares S.A. > C/Rita Levi **** > > Edificio SM2 Parc Bit**** > > 07121 Palma de Mallorca**** > > <http://es-es.facebook.com/pages/SM2-Baleares/158608627954> > <http://twitter.com/#!/SM2Baleares> > <http://www.linkedin.com/company/sm2-baleares> > > La información contenida en este mensaje de correo electrónico es > confidencial. La misma, es enviada con la intención de que únicamente sea > leída por la persona(s) a la(s) que va dirigida. El acceso a este mensaje > por otras personas no está autorizado, por lo que en tal caso, le rogamos > que nos lo comunique por la misma vía, se abstenga de realizar copias del > mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de > inmediato.**** > > P Por favor, no imprima este mensaje ni sus documentos adjuntos si no es > necesario. > > _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"
