Tim, I think he is looking not for the next one that the DB has, but the one that's already been allocated to the AR server and would be the next Entry ID for the next record actually created. In the current scenario, anywhere between 1 and 99 Entry IDs would have already been fetched from the DB and cached to EACH AR server you have, so the call would have to come from the actual AR server, not from the DB.
Rick Cook On Thu, Oct 12, 2017 at 1:47 PM, Hulmes, Timothy W CTR MDA/ICTO < timothy.hulmes....@mda.mil> wrote: > Thomas > > You can get this data from the "AR System Metadata: arschema" form. > > The fields of importance on this form: > Name = the Form Name > nextId = The next available ID for that form > > > Tim > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Thomas Miskiewicz > Sent: Thursday, October 12, 2017 2:14 PM > To: arslist@ARSLIST.ORG > Subject: What's the NextId? > > Hello List, > > with NextID Block size being set to 100 —> is it possible the find out > using the API which will be the next Request-ID that the server will assign > to a request? Or what other options do I have to find out? > > > --Thomas > > ____________________________________________________________ > ___________________ > 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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
