Mass Purge Dead Customers

otterhound
Member Posts: 16
We recently converted to Navision 4, running on SQL server. We imported all our customers from our old accounting system -- even those that had been inactive for years. We did not import any transactions for those customers.
Now I want to purge the dead customers from the Navision system. Is it safe to just run a SQL delete query on the customer table? Or are there other tables involved for a customer who has no transactions?
Now I want to purge the dead customers from the Navision system. Is it safe to just run a SQL delete query on the customer table? Or are there other tables involved for a customer who has no transactions?
James D Bennett
0
Comments
-
Never Insert/Modify/Delete data from a Navision table directly on SQL-server. You don't launch the triggers like that. Not updating flowfields, putting in data that is not according Navision-rules, ... :!: :!: :!: [-X [-X [-X
Except if it is a NEW table creating for inserting/modifying/deleting data from SQL.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
OK. Can you suggest another way to purge these customers so we don't have to do it one customer at a time?
Thanks!James D Bennett0 -
create a new blank report
first dataitem customer
onaftergetrecord trigger put
delete(true);
run the report. Set your filters on what customers you want to delete. and printpreview.0 -
Or, you run the Customer table from the object designer. From there, you set the filters that you want, select the customers you want to delete and hit the delete key.0
-
kriki wrote:Never Insert/Modify/Delete data from a Navision table directly on SQL-server. You don't launch the triggers like that. Not updating flowfields, putting in data that is not according Navision-rules, ... :!: :!: :!: [-X [-X [-X
Except if it is a NEW table creating for inserting/modifying/deleting data from SQL.
One small remark: If you are inserting data through direct SQL access, it will trigger Flowfield updates. 3.70 and 4.00 is using SQL triggers on tables to update the SIFT tables. This "SIFT is not updated" is only for older databases.
But that the data are not validated and that's why can data be wrong (for example lowercase characters in code field is disaster for Navision)...0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions