Hi all,
I have application that should be connected with Nav. In that application when somebody inserts new Customer, its passed to stored procedure in Nav's DB. With this stored procedure Customer is inserted as Contact.
First plan was to make Customer from Contact with Nav's report.
This solution is not good, and I want to ask you is Ok to create with this stored procedure Contact and Customer, and to insert this data into Contact Business Relations table? Can you guys give me pros and cons to do this?
tnx in advance.
0
Comments
-inserting data in the Navision-tables, you can completely mess up the data. (E.g. Code-fields don't exist in SQL and if you put a lowercase character in...)
-Business-logic is NOT triggered.
You should create a new table (without CODE-fields) in which the other application writes. Then let Navision transfer the data to the contact-table, respecting all the business-logic.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
This can be done by writing the data into a staging table, and have a NAV component process this into NAV core tables. It could also be done by sending the data as XML docs into a message queue and have a NAV process pick that up.
Get in touch with the NAV partner and discuss the options. Writing directly into the NAV database by a stored procedure is not the recommended approach.
RIS Plus, LLC
There is 1 NAS session included in the base product (at least for some time). Is your customer already using this? If not he already has one.
Tnx for your help
RIS Plus, LLC
This means if you insert records in contacts and customers, you do not have to worry about null values. Since the data is non-transactional, it is safe if you make sure you always insert fields in the proper format (CODE fields) and you meet the minumum requirements.
http://mibuso.com/blogs/davidmachanick/