** I just tried your idea. I get the following:
Next available ID produces an Entry ID that overflows Entry ID field --
contact the Administrator (ARERR 305)
This is probably because we already have 8000 rows in the form.
The idea is to have every year <some string>YEAR0001, <some string>YEAR0002,<some string>YEAR0003,<some string>YEAR0004, ...
So right now what I do is every year after the first ticket is created I export the row in a arx format. I manually make the change. Then import with the import tool.
And this way the next id gets the right format. And we are safe for the rest of the year.
But I'd like to have this self-service by Remedy itself.
I am starting to doubt in the power of this tool. So it has at least one limitation.



Conny Martin wrote:
**
this special run process wouldn't help you.
 
Documentation says: "Converts an internal representation of a qualifier into a qualification string using ID format. "
 
It deals with qualifiers not request_id formats.
 
What about setting the Default-Value of the request_id field to <some string>YEAR ? You have to adjust this every year, but it's simple.
 
Kind Regards Conny


Von: Action Request System discussion list(ARSList) [mailto:[email protected]] Im Auftrag von Remedy Maniac
Gesendet: Dienstag, 23. Dezember 2008 14:00
An: [email protected]
Betreff: how to use Application-Format-Qual-ID

** Dear listers,

some of my users would like to have a fancy Request_ID in the following format:
<some string>YEAR<Id number in 4 digits>
After many unsuccesfull attempts, I believe the Process Application-Format-Qual-ID could help
The problem is I don't get it work.
Could somebody give a hint on how to use this Process?
Or simpler, if anybody has a better idea, please share.
Thanks
Serouche


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

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

Reply via email to