Re: Created 15,000 tickets

[Susan Palmer]

**

Sorry, didn't notice you want to renumber some existing tickets for today.  If you're using something that uses the SHR:Consolidated form you need to make sure those records are updated also. 

 

Sounds like you may need a temporary field to hold the existing ID before any changes are made to that field if it is referenced in other forms or you loose that connection.  You could make this visible for reference if a customer provides that number also.

 

On 9/6/06, Susan Palmer <[EMAIL PROTECTED]> wrote:

I like to run the following statement before and after Lisa's command to make sure the change is effective

 

select name, nextId from aradmin.arschema where name = 'CHG:Task';

 

Initially you'll see what the system says is nextId, and then after the update you should see what you have now defined as the nextId

 

You are deleting all of those autogenerated tickets before you're resetting the ID or you will have unique record errors upon the creation of a ticket after the id is reset.

 

hth,

Susan

 

On 9/6/06, Nall, Roger <[EMAIL PROTECTED] > wrote:

**

Kathy,

 

Another trick is to create a view form to the arschema table. You can probably figure out what to do from there. No SQL involved. Just need to be careful.

 

HTH,

 

Roger A. Nall

OSSNMS Sr. Remedy Administrator/Developer

T-Mobile USA

Desk: 973-644-3963

Cell: 973-652-6723

FAX: 973-267-6628

sf49fanv     AIM IM

RogerNall   Yahoo IM

 

---

From: Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] On Behalf Of Kemes, Lisa
Sent: Wednesday, September 06, 2006 3:13 PM
To: arslist@ARSLIST.ORG

Subject: Re: Created 15,000 tickets

 

Here's the SQL that we use to reset the request id:  update ARAdmin.arschema set nextId = 1763 where name = 'FormName';

 

---

From: Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] On Behalf Of Kathy Morris
Sent: Wednesday, September 06, 2006 3:11 PM
To: arslist@ARSLIST.ORG
Subject: Created 15,000 tickets

**

Hi all,

 

Because some workflow had the wrong qualification from a previous developer, 15,000 tickets were generated.  We left off at 7,000 and now we are at 22,000.  Isn't there a way thru SQL to reset the value of the HPD to 7,000 so Remedy goes to set the next ID, it will think the last ID is 7,000.  We also want to rename the HPD tickets created today with a 7,000 value within the database. 

 

Our case ID is C1, I can find out the t table, I am just not sure which command I would enter to modify the rows in the database.  And if this will present problems later.  I know the users will be referencing the wrong ticket number.  We definitely do not want to be at 22,000.

 

 

__20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___