Development Musings (Mostly in Ax)

Tuesday, March 19, 2019

Ledger Dimension

I finally learned...A basic dimension is a default dimension. This is a value that concatenates a number of dimension values and is located in the Dimension Attribute Value Combination Table. If you add a Main Account, then you have a Ledger Dimension. The combination that you may try to retrieve or create MUST be part of the Main Account's Account Structure.

There are 2 approaches to getting a Ledger Dimension
1) Query it with AxdDimensionUtil::getLedgerAccountId
2) Create or retrieve it with DimensionDefaultingService::serviceCreateLedgerDimension

The code to retrieve a Ledger Dimension is:

private DimensionDefault getLedgerDimension(MainAccountNum _mainAccount, Num, str _bu, str _costcenter, str _dept)
{
    DimensionDefault result = 0;
    int position = 0;
    int dimensionCount = 0;
    container account;
    account += [_mainAccountNum, _mainAccountNum, 0];
    if(_bu)
    {
        account += ['BusinessUnit', _bu];
        dimensionCount++;
    }
    if(_dept)
    {
        account += ['Department', _dept];
        dimensionCount++;
    }
    if(_costcenter)
    {
        account += ['CostCenter', _costcenter];
        dimensionCount++;
    }
    account = conPoke(account, 3, dimensionCount);
    try
    {
        result = AxdDimensionUtil::getLedgerAccountId(account);
    }
    catch
    {
        return 0;
    }
    return result;
}

The code to called serviceCreateLedgerDimension requires a Main Account Number and Default Dimension:

private DimensionDefault getLedgerDimensionFromDefaultDimension(MainAccountNum _mainAccountNum, DimensionDefault _defaultDimension)
{
    DimensionDefault result = 0;
    DimensionDefault ledgerDimension;
    container account = [_mainAccountNum,_mainAccountNum, 0];
    ledgerDimension = AxdDimensionUtil::getLedgerAccountId(account);
    result = DimensionDefaultingService::serviceCreateLedgerDimension(ledgerDimension, _defaultDimension);
    return result;
}

Tuesday, March 12, 2019

D365 FO and External DLLs

We recently had to add some external dlls to our D365 for Finance and Operations model. We found out that when the references are added to a project, an XML descriptor of the reference is placed in $\LCS Dynamics Ax\Trunk\<your branch>\Metadata\<your model>\<your model>\AxReference. However, once you ready to deploy, the actual dll must be manually added to $\LCS Dynamics Ax\Trunk\<your branch>\Metadata\Bin. Otherwise, the LCS build will fail with a class not found error.

Friday, February 8, 2019

Positive Pay in D365 For Finance and Operations for 8.1

One of my clients recently upgrade to D365 version 8.1. This was a Microsoft mandated change as this is the one where overlays will no longer be allowed. After the dust settled, I was asked to make some changes to their Positive Pay files. The process worked in their previous environment, however under 8.1 the documents were being produced without data.

After debugging the process, I was able to isolate the issue to the MS side of code. Specifically, the DMF process was not able to find the required records. I raised a ticket with MS and they resolved it in short order. There appears to be a breaking change in 8.1 there the entity name must be capitalized in the XSLT file.

So instead of the old:

Document/BankPositivePayExportEntity

You need to put:
Document/BANKPOSITIVEPAYEXPORTENTITY

The documentation from MS has not been updated yet.

Wednesday, November 28, 2018

File Uploads in Dynamics 365 For Operations

I was recently reviewing some file import methods and I came across a new (for me) method of uploading files from a client. It turns out this is quite simple.

This calls a file finding dialog:
FileUploadTemporaryStorageResult uploadResult = Dynamics.AX.Application.File::GetFileFromUser();

This returns a System.IO.Stream:
System.IO.Stream stream = uploadResult.openResult();

These snippets were part of class that imported a 2 column spreadsheet in Excel. Please note that X++ now supports using statements. Here is the full code for reference:

using System.IO;
using OfficeOpenXml;
using OfficeOpenXml.Style;
using OfficeOpenXml.Table;
public class PayrollCodeImport
{
    public static void main(Args _args)
    {
        System.String value = null;
        OfficeOpenXml.ExcelRange cell = null;
        PayrollCode payrollCode;
        //upload
        FileUploadTemporaryStorageResult uploadResult = Dynamics.AX.Application.File::GetFileFromUser();
        PayrollCodeId payrollCodeId;
        Description description;
        if(!uploadResult)
        {
            return;
        }
        //construct a new spreadsheet document with the upload stream
        OfficeOpenXml.ExcelPackage package = new ExcelPackage(uploadResult.openResult());
        //OXMLSpreadsheetDocument_RU spreadsheet = OXMLSpreadsheetDocument_RU::constructFromStream(uploadResult.openResult());
        //get the worksheets from the workbook
        OfficeOpenXml.ExcelWorksheets worksheets = package.get_Workbook().get_Worksheets();
        //get the worksheet by name
        OfficeOpenXml.ExcelWorksheet payrollcodeWorksheet = worksheets.get_Item("Import") as OfficeOpenXml.ExcelWorksheet;
        //skip the header line
        for (int i = payrollcodeWorksheet.Dimension.Start.Row + 1; i <= payrollcodeWorksheet.Dimension.End.Row; i++)
        {
            value = null;
            cell = payrollcodeWorksheet.Cells.get_Item(i, 1);
            value = cell.Value;
            payrollCodeId = value;
            value = null;
            cell = payrollcodeWorksheet.Cells.get_Item(i, 2);
            value = cell.Value;
            description = value;
            if(payrollCodeId && description)
            {
                payrollCode.Clear();
                select forupdate payrollCode where payrollCode.PayrollCodeId == payrollCodeId;
                ttsbegin;
                if(!payrollCode.RecId)
                {
                    payrollCode.PayrollCodeId = payrollCodeId;
                    payrollCode.Description = Description;
                    payrollCode.insert();
                }
                ttscommit;
            }
        }
    }
}

Friday, August 24, 2018

Dynamics 365 FO Connection to ServiceBus

I recently received a request to connect D365 FO to an Azure ServiceBus in order to download messages that were being sent by another application. During the course of development, I found that there were 2 sets of projects that were developing connecting pieces: Microsoft.Azure.ServiceBus and Microsoft.ServiceBus. The first component, however, was tied to .Net 4.6.1 and D365 FO is tied to .Net 4.5.2. So, using the Azure component was out of the question. However there was no documentation on how to use the object model in the straight ServiceBus. Fortunately, both projects use a similar approach and a similar object model that I was able to make adaptations. There were 2 caveats.

D365 does not appear to work well with .Net async approaches.

D365 does not appear to work well with generics.

In order to get around this, I used a synchronous approach and passed any element that required using generics to a C# class that could do the processing. The Service Bus dll can be downloaded from https://www.nuget.org/packages/WindowsAzure.ServiceBus/4.1.11.

Once downloaded, open it as a zip file (you may need to change the extension to zip) and extract out the dll. Then add the dll as a reference in D365. Once there, the following class can be used to connect and download messages. Sending messages would use a similar logic. Please note that my requirements were to use Topics and Subscriptions rather than Queues. Also, please note that I save all of the connection parameters in a separate table. That way the system may access different Topic/Subscription combinations as required. Also, if the connection information is changed, then this can be reflected in data.

public class ServiceBusConnect
{
    public void new()
    {
    }
    public void receiveMessages(str _topic, str _subscription)
    {
        str strBody;
        System.IO.Stream stream;
        System.IO.StreamReader reader;
        Microsoft.ServiceBus.Messaging.SubscriptionClient subscriptionClient;
        Microsoft.ServiceBus.Messaging.MessagingFactory messagingFactory;
        Microsoft.ServiceBus.Messaging.BrokeredMessage message;
ServiceBusConnectionParameters parameters;

        select firstonly parameters where parameters.Topic == _topic && parameters.Subscription == _subscription;
ServiceBusConnector.BrokeredMessageProcessor connector = new ServiceBusConnector.BrokeredMessageProcessor();
        messagingFactory = Microsoft.ServiceBus.Messaging.MessagingFactory::Create(parameters.ConnectionString,
                Microsoft.ServiceBus.TokenProvider::CreateSharedAccessSignatureTokenProvider(parameters.SharedAccessKeyName, parameters.SharedAccessKey));
        subscriptionClient = messagingFactory.CreateSubscriptionClient(parameters.Topic, parameters.Subscription);
        message = subscriptionClient.Receive(System.TimeSpan::FromSeconds(5));
        if(message != null)
            setPrefix("Messages");
        while(message != null)
        {
            strBody = connector.GetBrokeredMessageContents(message);
            info(strBody);
            subscriptionClient.Complete(message.LockToken);
            message = subscriptionClient.Receive(System.TimeSpan::FromSeconds(5));
        }
        subscriptionClient.Close();
    }
}

The table ServiceBusConnectionParameters contains all the data for connection to Service Bus. The Topic and Subscription should be based on how your project's service is configured. The connection string will be sb://<your project>.servicebus.windows.net. The SharedAccessKeyName will be what ever is configured in your service bus. The default is RootManageSharedAccessKey. The shared access key is the primary key as displayed on your Service Bus Explorer.

As usual for using .net assemblies in D365, all class references must be fully qualified with their name spaces. The parameter in the subscriptionClient.Receive call is a timeout. If no messages are found within 5 seconds, the call is aborted and the message is set to null. Without it, the system just hangs indefinitely waiting for messages. The call to GetBrokeredMessageContents uses a call to the GetBody method on the message itselft. This method requires a generic reference to type the message. I could not, however, find a way to do that within D365. The wrapper to deserialize the message was pretty straightforward.

using System.IO;
using Microsoft.ServiceBus.Messaging;

namespace ServiceBusConnector
{
    public class BrokeredMessageProcessor
    {
        public string GetBrokeredMessageContents(BrokeredMessage message)
        {
            string strResult;
            using (var stream = message.GetBody<Stream>())
            {
                using (var reader = new StreamReader(stream))
                {
                    strResult = reader.ReadToEnd();
                }
            }
            return strResult;
        }
    }
}

Tuesday, June 5, 2018

Ax 2009 - Payment Journal Report Slow

We have a client on Ax 2009 and was saying that the Payment Journal Report was slow (not completing). One person in my group has seen the issue before. Her solution was:

Stop AOS
Delete CustVendPaymReport from SSRS
Restart SSRS service
Backup and delete XPPIL file contents
Start AOS
Redeploy custVendPaymReport
Run Full CIL
Run DB sync

I'm not sure why this works. My colleague seems to think it's because the report has an uncommitted transaction. However, if that were the case, restarting SQL Server would have solved it. Also, it does not explain why redeploying the report is part of the process.

I have 2 suspicions, but can't prove either. One is that the queries involved in gathering the data is missing a needed index. We tried running the Ola scripts to evaluate and rebuild statistics or reorg/rebuild indexes. That did not help. The other possibility is that somehow one of the db temp tables is surviving from run to run when it should not.

Dynamics 365 SSL Certificates Expire (HTTP 500)

I had a major issue today with my Impark local development environment. Whenever, I tried to start an instance, I kept getting an HTTP 500 (internal Server Error). Checking HTTP 500 with D365 got me nowhere. I finally looked in my Event Viewer, I found a number of errors related to Expired Certificates.

Exception information:

Exception type: ExpiredCertificateException

Exception message: Expired certificate for id '61EF4024783735137DBA51E341E36A0AE6A89497'.

Checking that, I was able to find that the SSL Certificates used by D365 had expired. It appears that the copy of my installation is a year old. Checking further, I was able to find a way to renew the certificates. Search and Open Manage Computer Certificates.

Select Personal -> Certificates. Look For the DeploymentOneBox entries.

For each, double click and go Details -> Thumbprint.

Copy and Paste the Thumbprint to Notepad. Put each entry on a separate line. When finished, replace all spaces with empty. Once you have all 4 numbers, you can create a power shell script. At the top of file, put:

Set-Location -Path "cert:\LocalMachine\My"

The for each Thumbprint, create the following 2 lines:

$OldCert = (Get-ChildItem -Path 2e10fea6fcd1a23d0ba5dfefe5ce2eb3d8915f1a)