Posted Documents

Saj

Dear All,

Can anyone please direct me to any official documentation/article/papers which would explain to why Navision deletes/archives documents (i.e. Sales/Purchase Orders) once posted. I have exhaustively looked around yet can't find anything, can anyone remember seeing it anywhere? Appreciate your input.

Many thanks

Marije_Brummel

I'm sorry, I know not of such document.

However, I can tell you that deleting the orriginal sales and purchase documents has everything to do with keeping the performance of the system going.

DenSter

I don't think it deletes archived documents, there's just no way in standard Navision to get to the archived documents. It's easy to add though, just copy the document forms and change the source table to the archived tables and you should be more than halfway there.

Saj

Mark Brummel wrote:

I'm sorry, I know not of such document.

However, I can tell you that deleting the orriginal sales and purchase documents has everything to do with keeping the performance of the system going.

Thankyou for your reply. I have checked various manuals including the development ones but to no avail. I agree the intentions behind this was to attain optimum performance. The reason behind my request was due to a client requesting for the original documents not to be deleted, just trying to prove a point to the client what the 'official' line is.

Saj

DenSter wrote:

I don't think it deletes archived documents, there's just no way in standard Navision to get to the archived documents. It's easy to add though, just copy the document forms and change the source table to the archived tables and you should be more than halfway there.

Thankyou for your reply, I was more after to why Standard Navision deletes Documents once posted, I know the intention was for performance reasons, just require the 'official line'.

DenSter

I don't know if deleting the documents was for performance issues, to me it seems like they do that because when orders are completely posted there's no reason to keep them around. It's easy to modify the system to keep them though. Just find the line of code that deletes them and comment it out.

Marije_Brummel

Yes, you can easlily comment it out, we've done so with a few small customers.

However, I've been involved with some large implementations where it was done, and there were some serious performance problems.

It all depends on how you use the system. There is no right or wrong way.

DenSter

What we've done before is automatically archive documents when they are released, and also right before they are deleted. That way you don't lose performance in the open document tables, and you still have a place to reference 'old' orders. Of course you will have to give users access to the archived ones from the menus.