The problem is that all updates are counted against the filter limit. So, if you have n records to be modified, and each modification causes m filters to run, you will get n*m filters total running in the transaction.
A simple solution may be to say no maximum number of filters temporarily while you execute the change. You can use Meta-Update on a trial license (no cost) and it will effect all changes. Because each update is a separate API transaction, the filter limit will not be reached as the total number of filters executed will be m - not n*m If you are interested in a trial (which will effect your changes - just specify both your production and development servers on the trial form), then please contact me off-list. Cheers Ben Chernys Senior Software Architect Description: logoSthInc-sm Canada / Deutschland Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: <mailto:Ben.Chernys_AT_softwaretoolhouse.com> Ben.Chernys_AT_softwaretoolhouse.com Web: <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com Check out Software Tool House's free Diary Editor and out Freebies Section for an ITSM 7.6.04 Forms and Fields spreadsheet. Meta-Update, our premium ARS Data tool, lets you automate your imports, migrations, in no time at all, without programming, without staging forms, without merge workflow. <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Boyd, Rebecca Sent: June-08-12 19:33 To: arslist@ARSLIST.ORG Subject: Re: Updating Service CI name ** Anne, It's been a while since we've talked. How are you? I am facing the same thing - renaming a Service CI - & found your old post. How did you rename your Service CI? What did you do? I am on ITSM 7.5. Rebecca On Fri, Aug 13, 2010 at 2:38 PM, Ramey, Anne <anne.ra...@nc.gov> wrote: ** My management wants to rename a service CI that's been used for a very active service for quite a while. It is associated with tens of thousands (if not hundreds of thousands) of tickets. The name change fails and it appears from system messages that it is reaching the top of the filter stack (we have this set to 10,000). I don't think doing the same action via escalation will help at all. It's not as if the name change happened and just didn't update all the association. The name change itself never completes. Is there no way to change the name of a CI that is associated with large numbers of tickets? ARS 7.1 p 6 CMDB 2.1 p 4 Anne Ramey *********************************** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ -- Rebecca Boyd Application Administrator Wake Forest University _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"
<<image003.jpg>>
smime.p7s
Description: S/MIME cryptographic signature
