Adding stored procedures to NAV 5 on SQL Server

davidec

Hello!
I need to integrate an existing web application with an existing NAV5 system, running on SQL Server. Some data need to be fetched from some definite NAV tables and some other data need to be written to other definite tables.

Since the web application already relies on Stored Procedures to access another SQL Server DB, I'm evaluating the possibility of adding custom stored procedures inside the NAV5 DB, calling them from the web application, and any implications of doing so...

I figure this would not cause problems reading data (as far as who calls the SP has sufficient rights, but this should not affect NAV users management, right?), whereas some issues could arise if, when writing, I fail to update all tables that would be afftected using standard NAV...

Are there any known issues in doing so? I should "just" take care of the rights accessing the DB and make sure that I don't leave tables untouched that would be affected by a standard NAV trigger?

Thank you very much in advance!

kine

When writing into NAV from outside, it is good practice to write data into separate tables, created only for that purpose, and process these tables into "live" tables by some NAV process (e.g. running on application server). In this way, you are sure that whole business logic is working and you will not mess the data...

davidec

Thank you very much: An interesting point that I'll need to take into account!