You will have to manually delete related records (Customer Ledger Entries etc...) and also fields that maintain a relationship (through Nav) to the customer table.
The customer table has a lot of delete-trigger code to delete extra tables and check if it can be deleted (if a customer has customer ledger entries, you can't delete the customer).
These tests/deletes in extra tables will NOT be done by a delete in SQL. So you can mess up a lot in NAV.
In short : DO NOT DO IT!
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
I have imported the list of customer in data migration, but i have not set the general posting grup. I want to delte all the list of customer that i have imported in nav and than to rimport. It a big list with 2000 customer it is very hard to do manualy all.
What is said about the problems incurred when deleting directly in NAV is true. Does anyone know where such information can be found to "make it official" that direct use of the SQL database is worst practice. Is there a white paper available or such that states that.
I am not questioning the knowledge of anyone, I am looking for facts to present to customers, prospects, SQL consultants etc. when they are attempting to do this and they need to see something in black and white to "prove" to them that it should not be done. In otherwords, to show a non-NAV person why they should not try this "easier" method.
thanks for any assistance you can offer on this request.
I have imported the list of customer in data migration, but i have not set the general posting grup. I want to delte all the list of customer that i have imported in nav and than to rimport. It a big list with 2000 customer it is very hard to do manualy all.
Thanks for your reply.
Can't you run Table 18 from Object Designer, select all records and press delete? :-k
Comments
You will have to manually delete related records (Customer Ledger Entries etc...) and also fields that maintain a relationship (through Nav) to the customer table.
You will get problems in Nav.
The customer table has a lot of delete-trigger code to delete extra tables and check if it can be deleted (if a customer has customer ledger entries, you can't delete the customer).
These tests/deletes in extra tables will NOT be done by a delete in SQL. So you can mess up a lot in NAV.
In short : DO NOT DO IT!
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Thanks for your reply.
I am not questioning the knowledge of anyone, I am looking for facts to present to customers, prospects, SQL consultants etc. when they are attempting to do this and they need to see something in black and white to "prove" to them that it should not be done. In otherwords, to show a non-NAV person why they should not try this "easier" method.
thanks for any assistance you can offer on this request.
Can't you run Table 18 from Object Designer, select all records and press delete? :-k