Futures class in Dynamics AX

-
In Dynamics AX, if you want to find a date in a period, chances are you would be using the DateTimeUtil class.

Say, I want to find the date 3 months exactly from today. Assuming a month is of 30 days, I can call the DateTimeUtil::addDays() method.

So my code to get that will be,
print DateTimeUtil::date(DateTimeUtil::addDays (DateTimeUtil::utcNow(), 3 * 30));

There is another application class in Dynamics AX, which does exactly this. This is the Futures class.

Let us see this class in action.
static void FuturesClass(Args _args)
{
    Futures     future;
    int         i;
    
    // Setup a future class object with 365 days as a period
    future = new Futures(systemDateGet(), 365, PeriodUnit::Day);

    future.next();    
    
    info(strFmt("Future date after 3 months from today is %1",future.transDate()));
    
    // Setup a future class object with 1 year as a period
    future = new Futures(systemDateGet(), 1, PeriodUnit::Year);
    
    for (i=1; i<=3; i++)
    {
        future.next();
    }
    
    info(strFmt("Future date after 3 years from today is %1",future.transDate()));
    
    // Setup a future class object with 1 month as a period    
    future = new Futures(systemDateGet(), 1, PeriodUnit::Month);
    
    for (i=1; i<=3; i++)
    {
        future.next();
    }
    
    info(strFmt("Future date after 3 months from today is %1",future.transDate()));    
}
The output is
The Futures class is initialized by passing three values. The start date of the period, length of the period and the Period unit. The Period unit can be day, month or year. So when we create a new object specifying today's date as the start date, 15 as the period and day as the unit, it means each period in this instance will be 15 days long. So if I call the future.next() method, I will get a date exactly 15 days from now.

So what are the advantages of this over the DateTimeUtil class? Well, the readibility of the code is obvious. Apart from this, you dont have to worry about missing days in a period and the extra calculation needed.

For example, lets say today is 23rd August. August has 31 days, September 30 and October 31 days. So we need to add 92 days in total, which gives us 22nd November. But if I need to use the DateTimeUtil class for that, I have to do the days calculation myself whereas the Future's class handles this automatically.

The Futures class is a nice little helper class which can be helpful when calculating periods of given length in days, months or years.

I hope this post was helpful. Do send me your comments.

Thats all for today, do check back soon.

Comments

Post a Comment

Popular posts from this blog

How to add empty ranges in query

-
In Dynamics AX programming, a common mistake I have seen when it comes to query ranges is passing an empty string value to the range. The developer here is expecting it to show all the records where the range field is empty. Instead, what we get is all records without the range being applied. As baffling as it may seems, it is easily explainable. The query engine in Dynamics AX, will not add a range if you don’t specify a value or if you specify an empty string because an empty string is treated as no value. So the following code will result in this SQL statement, query = new Query(); qbds = query.addDataSource(tableNum(ProjTable)); qbr = qbds.addRange(fieldNum(ProjTable, Name)); qbr.value(''); Select first fast * from ProjTable; But what was expected was something like, Select first fast * from ProjTable where Name == ''; So to work around this issue, use the SysQuery::valueEmptyString() static method which parses the empty strings correctly so that it...
Read more

The field with ID '0' does not exist in table - Cause and resolution.

-
Image
Hello readers, In Dynamics AX coding, you should have come across this error sometime - The field with ID '0' does not exist in table 'SomeTable' So what causes this error and what is the possible resolution to it? Well, the most likely cause for this error is a missing mapping in a table map. Let us look at an example. I've a simple Map named CustVendAccount with one Account field. I've created two mappings - one with CustTable's AccountNum field and for the otehr mapping, I just specify VendTable but no field. This is how my map looks like, Now, I've a simple job which just passes either CustTable or VendTable as an argument and then we print the Account field in the map. static void CustVendAccountMap(Args _args) { CustTable custTable; VendTable vendTable; void readMap(CustVendAccount _custVendAccount) { info(strFmt("Value from table %1 is %2",tableId2name(_custVendAccount.TableId), _custV...
Read more

Get selected records in Dynamics AX 2012

-
Image
In my earlier post, we discussed how we can retrieve all selected records on a list page. You can read that post here . Retrieving all selected records from a caller form is very easy. The code for this can be found in a number of places in standard Dynamics AX codebase. The general approach is to use the dataSource.getFirst(1) statement to get the first selected record and loop through the remaining using dataSource.getNext() . In Dynamics AX 2009, a new class was introduced for this purpose. This was the MultiSelectionHelper class. In Dynamics AX 2012, another new class has been introduced to retrieve the selected records. This is the MultiSelectionContext class. The MultiSelectionHelper class is an application class. It presents two constrcutors. The standard constructor method just creates a new instance of the MultiSelectionHelper class. When this construct is used, you will have to explicitly set the dataSource to be used for fethcing selected records. This can be done...
Read more