Petar Georgiev

Dear all,

I have the following situation with one of our clients:

They are using NAV to create documents and indexes for these documents. With DocuWare Import they are importing the image of the document in DocuWare and after that, using Autoindex, they fill in all the indexes in DocuWare. Sounds good, and works. But where is the problem - they have more than milion records in NAV, and are creating thousands of records every week (sometimes even thousands of records every day). Also, their server is heavy loaded. So they need to decide how to:

1. Read only the new records in NAV, by DocuWare Autoindex (not thousands of them);

2. Mark successfully processed records (by DocuWare Autoindex) in NAV so they don't need to be read again(this will be the best option);

I created an additional field in NAV database, which I can use as marker (1 - successfully processed, 0 - not processed). Created Autoindex which reads records in NAV, marked as 0. Then created second Autoindex, which reads records in DocuWare, newer than 1 day, and for them, updates the marker in NAV from 0 to 1. 

In this situation client has two Autoindex processes for one function. As I wrote, their server is heavy loaded and runing several autoindex processes at the same time is not OK. 

So, after these boring explanations, I want to ask You if You have any idea, how to manage this situation with less server load and more accuracy, because in my configuration, if the second Autoindex fail for some reason, there will be no sign in NAV.

I am waiting for your ideas.

Best Regards,

Petar

Josef,

Thank You! I will try this in our client test enviroment and check how it works. I think it will be fine, just to check the speed. Thanks again. 

Best Regards,

Petar

Josef,

Thank You for the idea. Unfortunately it is my fault that I missed one parameter of the project, that is not allowing me to create such 2 column table - the client has 1000+ users. Most of them (more than 600) have the right to store this kind of documents. So the table will contain too many rows, and administrators will not like this - to add(remowe) more than 600 rows in a table when user is hired(fired). I know there is an option for automatic update, but still not sure if it will work fine. 

That is why I asked if I can use SQL statement.

Maybe I can think of some validation (if it is possible) - store user not to be equal to some of the values in field Next Instance (yeah, Next Instance is keyword field). I will have to try it this way. 

Thanks again for the idea!

Hello,

I have the following situation: One of our clients wants to use the following restriction - while storing document (so it is in store dioalog), in the field Next instance, containing all users of DocuWare, the current user not to be able to choose himself. 

Example: If all users of the system are A, B, C, D, E, and user D is logged in, when he tries to store a document, and fill the field Next instance, to see only users A, B, C and E. 

I have an idea to use select list, with SQL Statement, looking like this: Select username from all_users Where username != currentuserlongname. The question is, how can I get the "currentuserlongname". Can someone tell me where the "currentuserlongname" is stored, and am I allowed to use it for select list like this. 

Also, if anyone has another idea, I'll be happy to hear(read) about it.

Thanks in advance!