** If there are attachment fields on your form don't forget to update the B tables. Kind Regards Conny
________________________________ Von: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] Im Auftrag von Joe DeSouza Gesendet: Mittwoch, 18. Februar 2009 19:42 An: arslist@ARSLIST.ORG Betreff: Re: Adding leading zeroes to Request ID ** The key is you will need to know your system well. If you want to do what you want to, you will need to know the different relationships that form might have with other forms (such as association tables if you are using the OTB applications etc), where the Request ID is used in the relationships.. Off course you also will need to modify the corresponding entries in the H tables as well. It would be possible to write a SQL script to achieve what you want so long as you know your system well.. Joe ________________________________ From: Rick Westbrock <ri...@petco.com> To: arslist@ARSLIST.ORG Sent: Wednesday, February 18, 2009 11:05:26 AM Subject: Adding leading zeroes to Request ID ** I ran into a problem today on a form where some previous admin had set the Request ID field (1) to only five digits so after case number 99999 was created the NextID value in the arschema table incremented to 100000 but the form obviously couldn't create a case with that number so the agents were seeing error messages. My backup admin bumped the field length up to six digits so that agents could immediately start logging tickets again but I plan to increase the field length up to 10 or 15 digits. My question for everyone is what is the best practice to go back and zero-pad all of the existing tickets with five-digit Request ID numbers? It's not strictly necessary for operations but when search results come up defaulting to sort by Request ID these new six-digit request ID cases come up at the top of the list which is not intuitive at all for end users. I do have a dev server on which I will test whatever method I decide upon first and I can delete records if needed as part of testing. -Rick Single Remedy application server: Windows Server 2003 SP 2 IIS 6.0 ARS 7.0.1 patch 6 E-mail Engine 7.0.1 p6 Mid-Tier 7.0.1 p6 Tomcat 5.5 Remote Database Server: Windows Server 2003 SP 2 SQL Server 2000 (8.0.76 SP 3 Standard Edition) _________________________________ Rick Westbrock PETCO Telecom Engineer ri...@petco.com <mailto:ri...@petco.com> __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"
