Re: Increasing Entry ID Length

[Joe DeSouza]

**

Actually I have noticed that by changing the sort order on the form, quite a few sort orders get altered.. For eg. the sort order on active links and filters when you do set fields to find first matching entries.. that gets altered as to which entry it finds first (I learnt that once the hard way round while developing a few years ago a few versions ago).. I do not think that has changed..

 

I do not remember if the sort order on table fields get altered too but I think it does..

 

Is there some sort order you were particularly addressing that does not get altered?

 

Joe

----- Original Message ----
From: Uday Joshi <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Thursday, September 18, 2008 1:50:10 AM
Subject: Re: Increasing Entry ID Length

**

Hi Joe,

 

That's definitely good idea.

 

However this will have to defined the form properties, otherwise by default the result list is sorted on the request ID.

 

Also there are questions from user community that why the list looks different. We can take out leading zeros mentally but system can not.

 

Still your idea is the most practical way.

 

Best Regards,

 

Uday Joshi

 

Delivery Manager - BSM Tech Support

Technology Infrastructure Services - BSM Unit

-------------------------------------------------------------------

Wipro Technologies,

Hinjewadi, Pune 411057

India

Tel: +91 20 39104092

VOIP 842-5103

 

 

---

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Thursday, September 18, 2008 01:18 AM
To: arslist@ARSLIST.ORG
Subject: Re: Increasing Entry ID Length

**

Uday, Ron,

 

A workaround to resolve this would be to sort the results by the Create Date rather than the Request ID..

 

Create Dates are usually in chronological order and there is a very very thin chance this may not be the case for consecutive requests that may have been created at about the same time...

 

Joe

----- Original Message ----
From: Uday Joshi <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, September 17, 2008 5:39:23 AM
Subject: Re: Increasing Entry ID Length

**

Hi Ron,

 

I had handled such situation in earlier assignment. There to avoid huge series of leading zeros we had limited size of request ID to 6.

 

There are few checks you will have to do

1) Check the "Input length" of this field.

2) Check column width of C1 at the data base level.

 

If at database level it is 15, then you can change input length to 7 or whatever number up to 15. Since the data base is already capable of handling larger data this change has least data. If both these have length as 6 then the table needs to be altered, which may create temporary load on the system.

 

In either case it is recommended that you do this activity in the lean time.

 

As soon as you save the form the new ID will be generated with the new length. If you have not hit the limit you will see leading zeros. It does not affect any old records.

 

The only visible problem is that since the request ID is stored and handled as a character the ones appended with zero comes on the top.

 

Example

 

0967991 (first with 7 digits)

0967992

0967993

967988

967989

967990 (last with 6 digits)

 

It would be a good idea to inform user community about this apparent incorrect ordering of tickets.

Later on you can append leading zeros to old cases by writing direct SQL at the data base level. However you will have to take of H and B table.

 

 

Best Regards,

 

Uday Joshi

 

Delivery Manager - BSM Tech Support

Technology Infrastructure Services - BSM Unit

-------------------------------------------------------------------

Wipro Technologies,

Hinjewadi, Pune 411057

India

Tel: +91 20 39104092

VOIP 842-5103

 

 

---

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ron [TBC]
Sent: Friday, September 12, 2008 08:23 PM
To: arslist@ARSLIST.ORG
Subject: Increasing Entry ID Length

**

Hi all,
Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1).  We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 999999.  What I want to do is to increase it to a length of 8.  Problem is that the existing ID's do not pad out to the full 8 digits.  Is there any utilities out there that makes this change easy and simple to do.  I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it.

Thanks in advance.

ARS 6.3 P.20
Win 2K3
SQL Server 2000

Thanks,

Ron Smith
Remedy/Web Developer
Providence Health & Services OR
[EMAIL PROTECTED]
503-216-7866

DISCLAIMER:
This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___