Monday, February 21, 2011

Effects of disabling a Configuration key for a table in AX 2012

Till AX 2009 version whenever the configuration key is disabled for a table the underlying table was dropped.

But now when you disable the configuration key for a table that is listed in the AOT in AX 2012, the corresponding table in the underlying database management system is not dropped.

Now when you modify a configuration key to disable a table in AX 2012, you must decide whether to manually delete the data that is in the table. External applications and Microsoft SQL Server cubes no longer break when you disable a table. They can continue to read the data from the table because they bypass the Application Object Server (AOS).

So, Folks the effect of disabling of Configuration key for a table in AX 2012 has been changed................................

3 comments:

AX Freak said...

Nice Info...Keep blogging abt AX2012.

Anonymous said...

I accidentally disabled a couple of configuration keys in Dax 2009...does this mean that the underlying data that was there is gone now? Or will enabling those keys rebuild the database....do I need to restore the data from a backup?

Giridhar Raj said...

yes exactly, When you enable those keys, it will rebuild the database but the data will be gone.....You need to restore the data from the backup to get the data back.............