Monday, July 3, 2017

AX 2012: Forms on opening hide behind in the back - 2° part

Hi Guys

About this topic the Microsoft workaround in some case doesn't helped me.
So, below you can find the code that definitely fix the issue!

Modify the StartupPost method of the Application Class and add these two lines:

if (hasGUI())
        Application::DisableWindowGhosting();


Lastly, created the "DisableWindowGhosting" static method like this:

client static void disableWindowGhosting()
{
    DLL DLL;

    DLLFunction DLLFunction;

    container con = WinAPI::getVersion();

    if (conpeek(con, 1) == 6) //Vista and Win7/Win2008R2 only
    {
        //this will disable window ghosting for this process only, for its lifespan only

        DLL = new DLL("USER32");

        DLLFunction = new DLLFunction(DLL,"DisableProcessWindowsGhosting");

        DLLFunction.call();
    }
}

That's it!

Sunday, July 2, 2017

MVP Dynamics AX/365 Renewal - Fourth time!

Hi Guys

For the fourth time I was able to remain MVP on Dynamics AX/365 for Finance and Operations.
Today We Kick Off Our First Annual Award Cycle. Congratulations to all Renewing MVPs!

It is not easy to balance career and remain an technology expert.
I guess that my trick is the passion!

Again is a pleasure stay on touch with the others MVP, meet them, share experiences, etc.

At the end, we became really a good friends!

See you on the next technical conferences, community websites, etc.

Lastly with the release of the Dynamics 365 for Financial and Operations on-premise, I guess we will have a lot of fun in the next months.

Friday, June 23, 2017

Microsoft Dynamics 365 Local Business Data aka On-Premise - Database Topology

Greetings

As you know Microsoft have release Dynamics 365 LBD - On premise version.

Dynamics 365 for Finance and Operations, Enterprise edition (on-premises) system requirements

About Database the main question is use SQL Server 2016 Standard or Enterprise Edition.
Obviously, refer to the Microsoft link in order to check the features supported by the SQL Server editions.

In a medium and not complex Project, my suggestion is to use the Standard Edition.
With the standard version is possible to setup an Always On Availability Group Cluster with a limit of two replicas (Primary and Secondary).

From a Business Intelligence perspective, we can setup a SQL snapshot on the Secondary replica and link to the snapshot the Reporting activities.

Stay Tuned!


Friday, June 9, 2017

Microsoft Dynamics 365 useful links

Hi

Below some useful links about Dynamics 365:

General Links:

1- Microsoft Dynamics 365 – Launch Portal

2- Introduction to Dynamics 365 for Operations

3- Overview of Microsoft Dynamics 365 for Operations for Developers and IT Pros

Evaluation Copy:

1- Get an evaluation copy
2- Try out Dynamics 365 for Operations now for free!
3- Have you given Microsoft Dynamics 365 for Finance & Operations, Enterprise Edition a try?

Database Management:

1- Copy a Dynamics 365 for Operations database from Azure SQL Database to a SQL Server environment For instance update Data from the UAT Environment to a Sandbox Environment.

On-Premise:

1- Dynamics 365 for Finance and Operations, Enterprise edition (on-premises) system requirements
2- Set up and deploy on-premises environments
3- On-premises deployment landing page
4- Features not implemented in on-premises deployments

Setup Dynamics 365 Virtual Machine

1- Setup Dynamics 365 for Operations Virtual Machine
2- Setting up a personal Dynamics 365 For Operations development environment
3- Virtual Machine(VM) setup to access Dynamics 365 for Operation instance
4- Running AX7 VM on Oracle VirtualBox

Hotfixes

1- Upgrades, Updates and Hotfixes in AX7

Warehouse App

1- Install and configure Microsoft Dynamics 365 for Finance and Operations – Warehousing

What's New

1- Microsoft Dynamics 365 Roadmap
2- What's new or changed

Unit Test

1- July 2017 update: Form Adaptors Replaced by Type Providers

Common Data Services

1- COMMON DATA SERVICES (CDS), DATA INTEGRATOR AND DYNAMICS 365, WHAT WILL YOU DO?

Ideas

1- IDEAS

This page will be update frequently!

Enjoy!

Sunday, February 19, 2017

AX 2012 - TFS multiple workspaces

Hi All

AX 2012 support only a single TFS workspace that mean a Dynamics AX Developer Box (SQL Server, AOS, etc.) for each developer.

Many of us use a Shared AX Environment, so many Developers connected to the same Dynamics AX Environment. More details at Microsoft Dynamics AX 2012 White Paper: Developing Solutions in a Shared AOS Development Environment

For this reason Martin DrĂ¡b created a custom Solution in order to help us to achieve this result, TFS workspaces in AX2012

This solution is fantastic.
The only issue is when an object is in check-out mode also other developers can modified it also if the check-in can only be handled by the check-out Owner.

In order to fix the behavior I have created a new method and modified another one in the SysVersionControlSystemFileBased Class.

Therefore:


Create a new method like “isCheckedOut” like this:

// AddaxWorkspaces
// Denis 20170219 - Check if the current Object is check-out by the current user
boolean isCheckedOut_dlx(Filename         _filenameCurrentLayer)
{
    Set                         checkedOutObjects = new Set(Types::String);
    SysVersionControlTmpItem    items;
    SysVersionControlSystem     sysVersionControlSystem;
    SysVersionControlParameters parameters = SysVersionControlParameters::find();

    str                         checkFileName;

    sysVersionControlSystem = SysVersionControlSystem::newType(parameters.vcsType);
    sysVersionControlSystem.init(parameters);

    if (sysVersionControlSystem)
    {
        items = sysVersionControlSystem.getCheckedOutItems();

        while select items
        {
            checkFileName = items.Filename;
            checkFileName = strReplace(checkFileName, parameters.AppRoot + '$\\' + parameters.TfsProject + "\\", "");

            if ( _filenameCurrentLayer == checkFileName )
                Return True;
        }

    }

    return false;
}

Modified the allowEdit method like this:

…..
        //Has the file been checked out
        if (!bitTest(WinAPI::getFileAttributes(filenameCurrentLayer), #FILE_ATTRIBUTE_READONLY)
        &&  this.isCheckedOut_dlx(filenameCurrentLayer)       // Denis 20170219 - AddaxWorkspaces
           )
            return true;

Thanks again to Martin and Stay Tuned!


Saturday, February 4, 2017

AX 2009 – SSRS Unable to connect to http://server/ReportServer/ReportService2005.asmx

Hi Folks

As you know, starting from AX 2009 was possible to use the SSRS Report instead of the Morphx Reports.

In the last weeks, I faced an issue during the Report Deployment. The error was:

Unable to connect to http://server/ReportServer/ReportService2005.asmx as specified in the config file for the report server at C:\…\RSReportServer.config. If this url is not correct please update the config file, otherwise make sure the report server is configured correctly.


Therefore, after some investigation and with help of Microsoft Support, I have fixed the issue.

Below what verify in priority order:

1-      Check if the Antivirus is enabled and in detail the Real-time scan. Disable it or create the relative rules

2-   Update the LanguageTable Table, field LabelFile. Only the languages with 1 on the LabelFile field will be deployed
            a.       select distinct LANGUAGE, HELPLANGUAGE from USERINFO
            b.   select * into LANGUAGETABLE_Backup from LANGUAGETABLE
            c.   update LANGUAGETABLE set LabelFile = 0 where LanguageId not in ('en-us', ‘it’)               //add any language found from first query

3-     Extend timeout settings
a.       Report Manager->Site settings->Report Execution Timeout->select “do not timeout report execution”.

b.      Increase the Timeout, so:
                                                               i.      Open “C:\Program Files\Microsoft SQLServer\MSSQL\ReportingServices\ReportManager\Web.config” and “C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\Web.config”
Search for httpRuntime executionTimeout="18000"

                                                             ii.      Open “C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\rsreportserver.config”
Search for:
1.       Add Key="SQLCommandTimeoutSeconds" Value="300"
2.      Add Key="MaxActiveReqForOneUser" Value="60"
3.       Add Key="DatabaseQueryTimeout" Value="300"

                                                            iii.      Increase these values as above, Restart SSRS Services and then test it.

c.       Update machine.config to speedup .net performance
                                                               i.      In C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\MACHINE.CONFIG, replace processModel autoConfig="true" with processModel maxWorkerThreads="100" maxIoThreads="100" minWorkerThreads="50"

                                                             ii.     In C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\WEB.CONFIG, locate the "system.web" Tag. Add the following as a child tag httpRuntime minFreeThreads="352" minLocalRequestFreeThreads="304" appRequestQueueLimit="5000"


Take care to make a backup of the configuration files before any modification!

Stay tuned!

Sunday, January 15, 2017

AX 2012 – TFS Build Error: The AXUtil command was started in the mode: export. Working against model store SQLServerName /ModelDatabaseName. ERROR: The file exists

Hi Guys

I am using the CodeCrib Library in order to handle my TFS Build Process.

During the last run, I faced the follow error:

Exception Message: Error exporting model: AXUtil 6.3 - Microsoft Dynamics AX Admin Utility (6.3.3000.2948) (c) Copyright, Microsoft Corporation, 2011. All rights reserved. The AXUtil command was started in the mode: export. Working against model store XXXXXX/XXXXXXX_model. ERROR: The file exists. (type Exception) Exception Stack Trace: at CodeCrib.AX.Manage.ModelStore.ExportModelShell(String modelName, String modelPublisher, String modelFile, String strongNameKeyFile) in c:\Users\xxxxxxxx\Documents\Visual Studio 2013\Projects\MainAxTFSLib\CodeCrib.AX.Manage\CodeCrib.AX.Manage\ModelStore.cs:line 144 at CodeCrib.AX.Manage.ModelStore.ExportModel(String modelName, String modelPublisher, String modelFile, String strongNameKeyFile) in c:\Users\ xxxxxxxx\Documents\Visual Studio 2013\Projects\MainAxTFSLib\CodeCrib.AX.Manage\CodeCrib.AX.Manage\ModelStore.cs:line 84 at CodeCrib.AX.TFS.ExportModel.Execute(CodeActivityContext context) in c:\Users\ xxxxxxxx\Documents\Visual Studio 2013\Projects\MainAxTFSLib\CodeCrib.AX.TFS\CodeCrib.AX.TFS\ModelStore.cs:line 96 at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
An error occurred while copying diagnostic activity logs to the drop location. Details: The file exists.

Resolution: You have to clean the TEMP folder related to the Agent User that will run the Build Process. 
Something like C:\Users\xxxxxxx\AppData\Local\Temp. After many TFS Build run, this folder contains a lot of files and an certain point the process try to create a file that already exist.

If possible, create a batch process that clean this folder at regular basis.

That is it!