2013 changes on CU-1 OnDatabaseXXX

Ninlil

In 2009 you could catch changes to the Object-table using these triggers in Codeunit 1.

For example:
This is how we could protect a customers production database from ever getting a "Modified" object in, thus protecting it from accidental editing and possibly objects that had not passed the testing database.

We could also create a "object change-log" every time a trigger caught a change, logging the object, user, action and timestamp.

Anyone know how we can catch this in NAV2013 since the Development Env. don't and can't run any C/AL at all?

ara3n

We have done it through sql triggers. There a couple of solution in mibuso download section.

Ninlil

Yes, we did this previously also (using an SQL-trigger on the Object-table), but the error-message to stop an invalid "modification" was so ugly that scared the customer (and us), and was very hard to actually see among the extra messages the NAV-client added to the messagebox.
That option is also a large magnitude harder to maintain than just updating CU-1 (and possibly a log-table)

Ninlil

An additional issue is that on NAV2013 you cannot in SQL catch what user is doing the modifications. :-k -> ](*,)

Ninlil

=D> Thanks Bardur Knudsen at NAVtechdays today that pointed out that since the NAV 2013 DevEnv directly connects to the SQL-server, an SQL-trigger can actually catch the real user modifying the Object table.