Question

Entry ID id is not continuous

Laserfiche

Updated April 21, 2015

asked on February 24, 2015

When I scan multiple documents continuously i can see that the document ID is not continuous. It skips 2 or 3 numbers. Why was the entry ID designed so?

I would like to know how to create a continuous ID to be used as metadata for documents in a repository

Regards

sweety

0 0

Answer

SELECTED ANSWER

replied on March 29, 2015

Sorry for the late response, I was out of the office for the week. Now that I'm looking at this question again, that method is probably not the best way to handle this situation mainly because of the inability to handle simultaneous requests. In case you're interested though, this is how you would do it:

Essentially you would have a document or folder that would be hidden from users. On that entry you will assign a field value. It can be whatever name you want. It should be a number field. The next step is pretty straightforward. It will look something like this:

Keep in mind that you should be assigning the number to something other than the Starting Entry. The image above is just an example.

This method will work fine for demos but I would not recommend it for a production environment. As Ben mentioned earlier, I would recommend using SQL to handle the incremental numbering.

0 0

Replies

replied on February 24, 2015 • Show version history

IDs can be skipped due to the internals of MS SQL Server (the id is an identity column which is auto-generated by SQL server). It sounds like you should use the %(GCount) token to achieve continuous IDs in metadata.

0 0

replied on February 24, 2015

Hi Sweety,

There is a Repository counter Laserfiche provides which is designed to be continuous. It's accessible via the %(GCount) token.

The EntryID is used for a number of different database objects (internal functions). In this case scanning a page has consumed an ID for the template and the page data.

-Ben

0 0

View 2 previous replies

replied on March 3, 2015

Is the GCount used for documents only?

0 0

replied on March 10, 2015 • Show version history

The %(GCount) token tracks whenever a entry is created in Laserfiche. This means it could either be a document or a folder. It is also only available when using Snapshot.

If you need to create your own unique # for documents, you can have a workflow assign a number as a hidden field value. You will just need to have a place holder somewhere in the repository that the workflow can retrieve and update for each new document that enters the repository.

0 0

replied on March 24, 2015

Hi Alan,

Can you please elaborate on what type of placeholder do I need to have for the workflow to be able to retrive its values.

Can you please provide a guide/ reading material for solution you proposed.

Regards

0 0

SELECTED ANSWER

replied on March 29, 2015

Keep in mind that you should be assigning the number to something other than the Starting Entry. The image above is just an example.

This method will work fine for demos but I would not recommend it for a production environment. As Ben mentioned earlier, I would recommend using SQL to handle the incremental numbering.

0 0

replied on April 21, 2015

I added simple synchronisation sequence to the WF to make sure that the ID is not repeated.

Thanks

Sweety

0 0

replied on February 24, 2015

Robert - "snap!"

0 0

replied on March 25, 2015

Sweety,

To be honest, when I need to manage contiguous numbers, I use SQL.

There's a bunch of ideas on Google.

Alan's idea could work but not sure how it handles simultaneous increment requests, which is why I go the SQL or %(GCount) routes.

-Ben

0 0

replied on March 30, 2015

Thank you for the script Ben. How do you relate it to LF then?

If we use GCount, then it won't be sequential as it will not apply to folders only but also metadata.

0 0

View 3 previous replies

replied on March 30, 2015

Can you explain what you are trying to do? %(GCount) is sequential and only incremented when it is used.

0 0

replied on March 31, 2015 • Show version history

Hi Sheila,

I would have a custom query activity call the SQL script as required when a counter is needed.

-Ben.

0 0

replied on March 31, 2015

Hi All,

@ Miruna: We want to automatically generate an ID which will be incremented by 1 for every created document across the repository.

Thanks

Kind Regards,

Sheila

0 0

replied on March 31, 2015

This has been asked in Sweety's duplicate thread: what is the purpose of the continuous ID and what significance would a gap have?

0 0

replied on April 1, 2015

It is a client's request that the ID should be continuous (i.e ID +1).

The purpose is that once the ID has been automatically generated for every document by Laserfiche, the client will write down the auto-generated ID on the physical files and the ID will be used as a referencing method.

Thanks

Kind Regards,

Sheila

0 0

replied on April 1, 2015

Hi Miruna,

We have configured the GCount. However, it is not incrementing by 1 but by 2. However, I believe that one is for the document and one for the metadata of that document. Is there any possibility where it can be incremented by 1?

Also, is it possible to reset the count as we are actually doing some testing on it? It will be more appropriate to start the counter when the project is live.

Thanks

Kind Regards,

Sheila

0 0

You are not allowed to follow up in this post.

Question

Question

Entry ID id is not continuous

Answer

Replies

Sign in to reply to this post.