Howard, As others on the thread have said, the 4k limit appears to be a database one. The 2k limit is a bug.
Chuck On Fri, Feb 13, 2009 at 9:53 AM, Howard Richter <[email protected]> wrote: > ** Chuck, > > Great news, bowever, is the size limit a bug with that patch or a new > feature going forward? > > Howard > > On Fri, Feb 13, 2009 at 9:45 AM, Charles Baldi <[email protected]>wrote: > >> ** >> All, >> I was able to update the table query in question. Here is what I did: >> >> 1. Downgraded my Admin tool to 7.1 patch 3 (thanks Conny). This allows >> creation of qualification strings up to 4k (4096 chars). >> >> 2. Since the OOB qual was already at 4081 chars, I could barely add the >> EXTERNAL() before running out of room. So I took the OOB qual and removed a >> pile of the superfluous spaces that the Admin tool adds to the qual, such as >> those around the "=", etc. This got the OOB qual down to 3727 chars. >> >> 3. Because I'm adding a half-dozen custom fields to the qual, the >> addition would still put it over the 4k limit, so I added another "AND >> EXTERNAL(custom_do_field)" and loaded my addition on Window Open. (thanks >> Scott and others). >> >> The real trick was to remove the extra spaces to make room. It is >> important to save a copy of the "compressed" qual for later because if you >> ever modify the table field, like to add a column, the Admin tool will barf >> again because it will have expanded the qual with the extra spaces again so >> that it exceeds the 4k limit. Saving a copy avoids having to remove all the >> spaces again. >> >> Thanks again, >> Chuck Baldi >> >> >> >> On Thu, Feb 12, 2009 at 9:22 AM, Charles Baldi >> <[email protected]>wrote: >> >>> Thanks for all the suggestions. I will see what I can get to work. FYI >>> my Admin tool is at 7.1p4 while the ARServer is at 7.1p5. >>> >>> I will let you all know the result. >>> >>> Regards, >>> Chuck Baldi >>> >>> On Thu, Feb 12, 2009 at 7:17 AM, Carey Matthew Black < >>> [email protected]> wrote: >>> >>>> However, you should also be warned that in at least a previous version >>>> (v5 or was it v6 era) there was a practical limit to the length of >>>> these qualifications. I was never clear if it was a RDBMS limitation >>>> or an ARS limitation, but I remember a number like 4000 characters as >>>> an upper limit to what actually works. Which was true even if you used >>>> the EXTERNAL() operator. >>>> >>>> -- >>>> Carey Matthew Black >>>> BMC Remedy AR System Skilled Professional (BRSP) >>>> ARS = Action Request System(Remedy) >>>> >>>> Love, then teach >>>> Solution = People + Process + Tools >>>> Fast, Accurate, Cheap.... Pick two. >>>> >>>> >>>> >>>> On Wed, Feb 11, 2009 at 6:45 PM, Scott Illari <[email protected]> >>>> wrote: >>>> > ** >>>> > >>>> > Chuck, >>>> > >>>> > >>>> > >>>> > I would follow these steps >>>> > >>>> > 1) Create a hidden display only character field on >>>> the >>>> > form. Just be sure the DB size of the field is 0 to hold the >>>> qualification >>>> > if it ever grows. >>>> > >>>> > 2) Update the table field so the qualification is >>>> > EXTERNAL($Display Only Field$) >>>> > >>>> > 3) Have an Active Link set the display only field on >>>> Window >>>> > Open or Display or Loaded (Whichever works for you) >>>> > >>>> > 4) Have the next action perform a Change Fields that >>>> > refreshes the table. >>>> > >>>> > >>>> > >>>> > Hope that helps. >>>> > >>>> > >>>> > >>>> > Scott Illari >>>> > >>>> > 908-601-8948 >>>> > >>>> > http://www.linkedin.com/in/scottillari >>>> > >>>> > >>>> > >>>> > From: Action Request System discussion list(ARSList) >>>> > [mailto:[email protected]] On Behalf Of Charles Baldi >>>> > Sent: Wednesday, February 11, 2009 5:30 PM >>>> > To: [email protected] >>>> > Subject: How to save huge qual string in Table / Tree Property? >>>> > >>>> > >>>> > >>>> > ** >>>> > >>>> > Hello all, >>>> > >>>> > >>>> > >>>> > I am trying to update the Table / Tree Property on the HPD:Incident >>>> Assoc >>>> > Search form to let users search for some of their custom fields. >>>> However, >>>> > the Qualification string is so large that the Admin tool will not let >>>> me add >>>> > to it. I can't even re-paste the original qualification back into the >>>> field >>>> > if I remove it. So, BMC must have a trick for pasting a HUGE >>>> qualification >>>> > string here. >>>> > >>>> > >>>> > >>>> > Does anyone know how to do this? >>>> > >>>> > >>>> > >>>> > ARS 7.1 p5 >>>> > ITSM 7.0.03 p8 >>>> > >>>> > >>>> > >>>> > Thanks in advance, >>>> > >>>> > Chuck Baldi >>>> >>>> >>>> _______________________________________________________________________________ >>>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >>>> Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" >>>> >>> >>> >> __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ >> > > > > > -- > Howard Richter > Red Hat Certified Technician > CompTIA Linux+ Certified > ITIL Foundation Certified > E-Mail = [email protected] > LinkedIn Profile = http://www.linkedin.com/in/hbr4270 > __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
