Tree node and Icons for tree nodes are inseparable. Right icons can make your tree look lot different.. Here is one tweak for getting the difference.

This article deals with displaying external images as tree node icons.

Images used in Treenode should be passed as Imagelist. Ax has set a predefined set of classes starting with ImageListAppl that helps to manage different sorts of ImageLists. ImageListAppl is the base classes of all such classes.

The most appropriate way to enable a strong support for external images in tree node would be through modifying the ImageListAppl class to load external images. (Currently they can load only resource numbers). The following code below when added to the base class helps you load images externally or through resource nodes.

public void addImage(int _idNo, FilePath _filePath)
{
    int imageNum;
    Image image = new Image();
    try
    {
        if (_filePath)
        {
            image.loadImage(_filePath);
            imageNum = imagelist.add(image);
            imageConvert.insert(_idNo, imageNum);
        }
    }
    catch
    {
        warning(strfmt("@SYS85977"));
    }
}

Now let’s see the usage of the method we added. Take a class like ImageListAppl_Sales for example. Override the build method and implement in the way as you seen below.

this.I4C_addImage(#ImageNewPic, SysResource::getImagePath('myimage')); 

Every Image loaded has to be identified through some resource numbers. Generally it is better if the new resource number you assign is greater than the system defined resource number.To identify the Highest resource number always refer to the  “SysImageResources” form. (4.0 users you can use the Tutorial_resources form).

Two things to note from the above line of code.

-> The new Resource numbers has to be defined as a macro in a new macro node or to an existing macro node like resappl (it contains the standard resource number).

-> In the above example i have used an image from the resource node, you can also use an external image which is stored in the computer. (Resource node is preferred, coz it is easy to distribute)

To use this image all you need to do is just load the same Image list class with your tree control and then just refer to the new resource number for the image that you wanted to display.

salesLineTree.setImagelist(imageList.imageList());
SysFormTreeControl::addTreeItem(salesLineTree, displaystring, 0, 0, #myImage);

That’s what it takes to our new image to the tree node. So now you can widen your image space for tree icons with all kind of images you like…

Keep reading… :)

So How did you read the title? “I Foresee for Dynamics Ax” …. that’s right, but still it has more subtle meaning to it.Keep reading to know more.

I4C also stands for “Innovites for Cable for Dynamics Ax”, the new add on that I(We) 4 C for Dynamics Ax. I4C(I Foresee) I4C  (Innovites for Cable) taking Dynamics Ax to a niche market, that’s cable industries.

It’s perfect to understand why Dynamics Ax was chosen as the platform for I4C before sharing the speciality of the solution.

Why Dynamics Ax?

Dynamics Ax is the right entrant to the market at the right time. This statement might make you raise your eyebrows. But that’s the fact. The market dominant ERP’s of the 1990’s like BAAN where widely implemented in many companies. These implementations have got quite old and the product companies of the ERP’s are not brisk enough to keep in phase with the changes that have happened mean time. So the companies that are looking  for a replacement have the following objectives to choose an ERP.

1. A product that exactly fits the existing technology stack.
2. A wider vision that ensures a long time support.
3. Cost Effective
4. Good manageability.

If Ax as an ERP can be scored against these needs, I’m sure that it would make up to a very good score. That simply defines in a few lines why Ax is the Platform for I4C

What I4C promises to deliver..

I can remember long time back having a discussion with some of my colleagues on what it takes to implement a Ax for a new Industry. The answer was pretty simple customize Ax to fit their process and implement. I did nod to it. But today if you would put forward the same question before me, I would definitely not give the same answer. Why do you need to go for new System if it is exactly reciprocating your process. Do you really need it ? What value addition has it got it for you ? That’s were the real reason behind the industry verticals stand.

Build a solution that doesn’t just reciprocate but enhances, add value to the existing process and make it more reliable. That’s the promise I4C carries.

I4C promises to inspires business innovation and create the changes to give room for the innovation and execute the change for excellence.

I4C I4C as a Industry solution that Innovates, Renovates and Implements the best fit process for cable industry.

Simply to say …………..

Keep checking this space….as I take you further in to the journey of Innovites’ Innovation.

It’s exactly 2.5 years from the time i began my journey along with Dynamics Ax. I got in to Sonata as  a fresh graduate after my engineering degree. I was made part of the Dynamics Ax practice, being a hardware enthusiast during my graduation days I had little knowledge on “OOPS” (I knew only to say “oops”). So the journey with Ax @ Sonata was much a action packed one, with lots of stuff to learn and lots to explore. The journey was much more interesting when Sonata identified me for my efforts and put me on better roles. I played roles from being a test developer to a lead guiding a large vertical development.

It’s now few weeks since I have got myself out of Sonata to run towards my long term wish. But I sincerely feel that I am much obliged to Sonata for the opportunities  and space that  I was given. It was a hard decision to make, which I am still refusing to believe.

It’s time to talk about the new role that I have picked up. I am now part of the team that has set steps to build a cable solution on Dynamics Ax. I’m much exited about this new role as it was something that I wished to do after becoming an DAx’er (I mean an Ax guy). So get prepared to here more from me and the cable solution that we are building…..

I know you would be now much interested to know more on the cable solution and the people behind it. Just click here to quench your quest …. www.innovites.com

    sysRecordTemplate = SysRecordTemplate::newCommon(inventTable); 
    sysRecordTemplate.parmForceCompanyTemplate('Feed'); //Template name as string
    sysRecordTemplate.createRecord();

//Call this method in the init method of form
SysRecordTmpTemplate VCTInitItemTemplates()
{
    Container               recordValues;
    ;

    recordValues = SysRecordTemplateTable::find(tablenum(inventTable)).Data;
    recordValues =  condel(recordValues,1,1);
    //tmp1 - Global variable for lookup    
    SysRecordTmpTemplate::insertContainer(tablenum(inventTable), tmp1, recordValues, SysRecordTemplateType::Company, true);
    //tmp2 - Global variable for validation
    SysRecordTmpTemplate::insertContainer(tablenum(inventTable), tmp2, recordValues, SysRecordTemplateType::Company, true);
    return tmp;
}


//Override the lookup method
public void lookup()
{
    SysTableLookup          sysTableLookup;
    SysRecordTmpTemplate    tmp;
    Container               recordValues;
    ;

    super();
   
    sysTableLookup = SysTableLookup::newParameters(tablenum(SysRecordTmpTemplate), this);

    //Add the fields to be shown in the lookup form
    sysTableLookup.addLookupfield(fieldnum(SysRecordTmpTemplate, Description), true);

    sysTableLookup.parmUseLookupValue(false);
    sysTableLookup.parmTmpBuffer(tmp2);
    // Perform lookup
    sysTableLookup.performFormLookup();
}       

//Override the modified method
public boolean modified()
{
    boolean                 ret;
    SysRecordTmpTemplate    tmp;
    container               recordValues;
    ;

    ret = super();

    select firstonly tmp2 where tmp2.Description == this.valueStr();

    if (!tmp2 && this.valueStr())
    {
        this.text('');
        warning ('Invalid selection.');
        return false;
    }

    return ret;
}

----------- any template for codes where i can just get all the code that i want

 Here guys the Autozip for Dynamics Ax 4.0 which i promised a long time back (click to see my promise).

 1. Dowload and Extract the zip file from the following place...
 2. Add the dll file from the extract to your bin directory and simlarly add an reference to it in your AOT
 3. Now import the XPO.
 4. Autozip is ready to use.

              
 

 How to import a zip file
 
 1. Just open any drive and point to a zip file that contains xpo's(doesn't matter if it contain other files inside it also)
 2. That's all ... all xpo files inside the zip will be imported.
 
Can you use this for your own custom development?

The Class "Infolog" has few methods corresponding to "Last activated form" like
 
                       - activate
                      -  setLastActivatedForm
                      -  parmLastActivatedForm
                      -  close
 
     These methods help in you knowing, setting or getting the currently active form.
 
       Say you have a form like "Toolbar" or  "Popup" form like Alerts or "Find" then you would prefer to prevent these form from being added to the lastactivated form. In such cases all you have to do is go to the "activate" method in infolog and add the following code

    if (formRun.name() != formstr(DocuView) &&
        formRun.name() != formstr(sysFormSearch) &&             
        formRun.name() != formstr(EventAttentionGrabber) &&
        //added by kamal
        formRun.name() != formstr(MyForm)        
       )
    {
        this.setLastActivatedForm(formRun);
    }

  This would skip adding your form to the last activated form list.

...................