Is it possible to archive in some way or another Customers, Vendors and Items? For example rather than simply blcoking a customer I want it to be removed from all reports and list.
We routinely archive information into a separate database through data exports and sql, though. Items that haven't been sold or purchased in years, customers that haven't bought anything.
It's tricky, though. You have to know all the tables to hit. Like archiving customers, you need to check customer ledger entries, detailed customer ledger entries, etc. It can throw things off if it's not done right.
Is it possible to archive in some way or another Customers, Vendors and Items? For example rather than simply blcoking a customer I want it to be removed from all reports and list.
The best way to go about it is to modify the reports and forms so blocked customer does not display.
Add A VAriable "Form Filters" type option
Options are: All Accounts,Active Accounts,Blocked Accounts
Now add a textbox at the bottom right of the form.
remember...Change Glue To BOTTOM
Sourceexp of the textbox willbe "Form Filters"
add the code to the textbox (you can use a case statement too)
OnAfterValidate()
IF "List Filters" = "List Filters"::"All Accounts" THEN BEGIN
RESET;
END;
IF "List Filters" = "List Filters"::"Active Accounts" THEN BEGIN
RESET;
SETRANGE(Blocked,FALSE);
END;
IF "List Filters" = "List Filters"::"Blocked Accounts" THEN BEGIN
RESET;
SETRANGE(Blocked,TRUE);
END;
CurrForm.UPDATE;
Most list forms are uneditable so to get around that..
add this to the textbox triggers.
Is it possible to archive in some way or another Customers, Vendors and Items? For example rather than simply blcoking a customer I want it to be removed from all reports and list.
The best way to go about it is to modify the reports and forms so blocked customer does not display.
make sure you add indexes, otherwise you will run into performance issues.
Also the users will need to get trained on how to change keys when they start adding additional filters.
Merging customers I would say is a better solution. You can have one generic customer called Archived, and merge all the other customers into it.
Ahmed Rashed Amini
Independent Consultant/Developer
Can't say that I like the merging idea. Certainly it's easier, but what about historical data? You're basically wiping out the whole history of that customer (or vendor, item, whatever). And once it's merged there's no going back.
I guess it's a trade off, though. If your company will NEVER need that data again (mine always needs old data for something) then it's fine.
I agree that there's really no need for it, but it started before I came on board at my company. I have not yet been able to convince them that they don't need to.
But their argument is that they still need that data, just not in every report or view they have. So we basically only keep 4-5 years worth of data in our production database (been on NAV for 10+). And every few months or so we'll have to pull some of that data from another database for them.
Comments
We routinely archive information into a separate database through data exports and sql, though. Items that haven't been sold or purchased in years, customers that haven't bought anything.
It's tricky, though. You have to know all the tables to hit. Like archiving customers, you need to check customer ledger entries, detailed customer ledger entries, etc. It can throw things off if it's not done right.
My Blog - nav.education
You can use the following tool to do this.
viewtopic.php?t=15580&highlight=merge+customer
This allows you to merge the customer into one customer
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
The best way to go about it is to modify the reports and forms so blocked customer does not display.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
Add A VAriable "Form Filters" type option
Options are: All Accounts,Active Accounts,Blocked Accounts
Now add a textbox at the bottom right of the form.
remember...Change Glue To BOTTOM
Sourceexp of the textbox willbe "Form Filters"
add the code to the textbox (you can use a case statement too)
Most list forms are uneditable so to get around that..
add this to the textbox triggers.
Save->Complie->Enjoy
http://www.BiloBeauty.com
http://www.autismspeaks.org
make sure you add indexes, otherwise you will run into performance issues.
Also the users will need to get trained on how to change keys when they start adding additional filters.
Merging customers I would say is a better solution. You can have one generic customer called Archived, and merge all the other customers into it.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I guess it's a trade off, though. If your company will NEVER need that data again (mine always needs old data for something) then it's fine.
My Blog - nav.education
If that's true, why archive in the first place?
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
But their argument is that they still need that data, just not in every report or view they have. So we basically only keep 4-5 years worth of data in our production database (been on NAV for 10+). And every few months or so we'll have to pull some of that data from another database for them.
My Blog - nav.education