Microsoft Dynamics AX

  This blog post is about exploring the new Microsoft feature that allows you to run X++ jobs on PROD and non-PROD environments without release and with 0 downtime. In 10.0.25 you can run simple X++ scripts on a production environment without any downtime. This feature lets you run custom X++ scripts without having to go through Dynamics LCS or suspend your system. Therefore, you can correct minor data inconsistencies without causing any disruptive downtime. To be able to use this feature   you need to create a deployable package with ONLY ONE runnable class in it. To do this,   you can create a new model and reference the models which object you will use in the X++ script.   Dynamics365->Model Management -> Create Model Ex: CutomModel  Then create the runnable class and generate a deployable package from Visual Studio only with your new model that has only one runnable X++ class. class SLWrongVendorRunnableClass {          ...

  Restoring a Dynamics 365 finops database has become much easier with the export database functionality in LCS. More details   here   With the new feature in LCS the database is exported out of Azure SQL and a bacpac file is added to the asset library After the database is exported the database file can be seen in the Asset library. The following steps can be used to import the database to development environment for Retail testing/debugging   1) Restore the bacpac file   SqlPackage.exe /a:import /sf:D:\EXPORTED-DB.bacpac /tsn:localhost /tdn:AxDB_Copy /p:CommandTimeout=1200   2) Stop the world wide publishing service, Batch, DIXF and management reporter service   3) Rename the original database to AXDB_Orig and database imported to AxDB   4) Start the services stopped in step2.   5) In the imported database the change tracking will automatically be turned off at database level. Enable change tracking on AxDB. This can be easily done fro...

 https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/dbmovement-scenario-exportuat Import the database: Keep a copy of the existing AxDB database, so that you can revert to it later if you must. Import the new database under a new name, such as  AxDB_fromProd . Open a  Command Prompt  window, and run the following commands from the sqlpackage .NET Core folder. Download sqlpackage .NET Core for Windows from  Get sqlpackage .NET Core for Windows .  SqlPackage.exe /a:import /sf:D:\Exportedbacpac\my.bacpac /tsn:localhost /tdn:<target database name> /p:CommandTimeout=1200 Update the database Remember to edit the final  ALTER DATABASE  statement so that it uses the name of your database. CREATE USER axdeployuser FROM LOGIN axdeployuser EXEC sp_addrolemember 'db_owner', 'axdeployuser' CREATE USER axdbadmin FROM LOGIN axdbadmin EXEC sp_addrolemember 'db_owner', 'axdbadmin' CREATE USER axmrruntimeuser FROM LOGIN axmrruntimeus...

 USE AXDB;   GO   -- Truncate the log by changing the database recovery model to SIMPLE.   ALTER DATABASE AXDB SET RECOVERY SIMPLE;   GO   -- Shrink the truncated log file to 50 MB.   DBCC SHRINKFILE (ProdAXDB_log, 50);   GO   -- Reset the database recovery model.   ALTER DATABASE AXDB SET RECOVERY FULL;   GO