Hi,
The standard setting since 7.6.04 is to have Next-ID-Block-Size: set to 25.
You have to reset this to 1 to disable this, but that might have a slight
impact on performance. This can be set in the ar.conf/cfg file or in the
Server Information form on the Configuration tab.
If you have Next-ID-Commit: set to F, it will definitely affect perfromance on
creates. But this defaults to T, which is ok if you can live with a few
missing Request IDs now and then (typically after filter errors during
submit).
You can however set the Next-ID-Block-Size to 1 on a form basis. This is done
on the form properties Basic section.
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> If you find that setting, please let me know where it is :)
>
> William Rentfrow
> [email protected]
> Office: 715-204-3061 or 701-232-5697x25
> Cell: 715-498-5056
>
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]] On Behalf Of Carl Wilson
> Sent: Wednesday, January 07, 2015 6:41 PM
> To: [email protected]
> Subject: Re: Determining first workinfo entry
>
> **
> Then I would adjust the SG so this does not happen ☺
>
> ________________________________
>
> Kind Regards,
>
> Carl Wilson
>
>
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]] On Behalf Of LJ LongWing
> Sent: 08 January 2015 00:21
> To: [email protected]<mailto:[email protected]>
> Subject: Re: Determining first workinfo entry
>
> **
>
> Unfortunately the request id can be our of sequence in a server group
> situation
> On Jan 7, 2015 5:06 PM, "Carl Wilson"
> <[email protected]<mailto:[email protected]>> wrote:
> **
> Hi,
> You could also use the request ID as it will be sequenced, there are existing
> joins available for Incident / Work Info that can be utilised.
>
> ________________________________
>
> Kind Regards,
>
> Carl Wilson
>
> http://www.missingpiecessoftware.com/
>
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of LJ
> LongWing
> Sent: 07 January 2015 21:38
> To: [email protected]<mailto:[email protected]>
> Subject: Re: Determining first workinfo entry
>
> **
> do a MIN on the create_date for the work log entry...this'll ensure you only
> get the first entry.
>
> On Wed, Jan 7, 2015 at 2:33 PM, Scott Hallenger
> <[email protected]<mailto:[email protected]>> wrote:
> Hi I am creating a report via sql, that would show several incident fields and
> 2 fields fromn the HPD:Worklog forms. Naturally this would be a join, but I am
> trying to figure out which is the best way to single out the first/earliest
> workin info entry and exclude the rest. As you know the worklog can have more
> than one entry related to the single incident. Any Ideas would be helpful.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at
> www.arslist.org<http://www.arslist.org>
> "Where the Answers Are, and have been for 20 years"
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> ________________________________
> No virus found in this message.
> Checked by AVG - www.avg.com<http://www.avg.com>
> Version: 2014.0.4794 / Virus Database: 4253/8799 - Release Date: 12/24/14
> Internal Virus Database is out of date.
> _ARSlist: "Where the Answers Are" and have been for 20 years_
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
