Joe, Now that is down right fascinating to me.
We were having problems moving our forms from v6.3 (patch 22 or 25) to v7.1 Patch5 unless we used the XML form of the object file. ( And now I am having problems trying to get some of the filters to import in the XML form.) I guess I will try the def file format and see if that works better. GRRRRR... In fairness however, we are also moving from Sybase to Oracle at the same time we are moving from ARS v6.3 to v7.1 and moving from Solaris to Linux too. So we have stumbled into a few other problems due that those other layers changing too. GRRRR.. But thanks for sharing the pain everyone. I now have a new path to test. :) ccrashh, By the way... Are you also using Oracle as your RDBMS? The reason I ask is that 4000 is a special number and we bumped into a problem with a Set field Qualification trying to search a field that was longer than 4k in length. So I wonder if your problems are more RDBMS centric than ARS centric. Just a thought. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Mon, Dec 22, 2008 at 1:31 PM, Joe DeSouza <[email protected]> wrote: > ** > Wanna know another interesting bug? > > Try exporting an AL that has a really long Set Field If qualification as a > .xml export, and then reimporting it again. The import will fail. I > experienced that a couple of weeks ago and was beating my brains numb as to > why the import was failing on that AL only and not others. And the only > different thing about that AL compared to any other that exported and > imported well was that qualification length. > > Exporting and importing it as a .def file, it has no problem. > > There is nothing wrong with the xml format but yet for some reason the > import fails. The reason why I wanted a xml export and not a def, is that > there were some modifications I needed to do on the def file which is easier > in the xml format than the def. > > Joe > > ________________________________ > From: ccrashh <[email protected]> > To: [email protected] > Sent: Monday, December 22, 2008 12:08:47 PM > Subject: Interesting "Bug" in 7.1 > > If you create a SET FIELDS action in an Active Link on a form with a 0 > byte (unlimited) field using the 6.3 version of the Admin tool (even > if the server is 7.1), you can cut and paste or type several thousand > characters (try about 4000). If you try to do the same thing in an > Active Link, on the same form and field, with the 7.1 Admin Tool, it > will not let you cut and paste and/or type more than about 1900 > characters into the SET FIELDS action. Give it a shot. Truly fun. > > The problem is worse than that....you can import such an Active Link > onto a 7.1 server, no problem. You just can't modify the set fields > itself. > > You can't run Remedy Developer Plus from the 7.1 Admin tool against it > either. It will hang the minute it hits that active link. > > Fun times. You can imagine the run-around I got from BMC Support. I > had to debug and solve this myself. > > Now...is this a bug in 7.1 or something BMC/Remedy "fixed" because it > was "not working correctly" in 6.3? _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
