RSS

AX2012R2 CU7: Email reports to specific people by using tokens

Ability to email reports to specific people by using tokens
In cumulative update 7, you can email reports to specific people by using tokens. When you use this feature, you don’t have to enter the email addresses of all recipients. Instead, you just enter a token. The token instructs Microsoft Dynamics AX to retrieve the appropriate email addresses from worker, customer, or vendor records.
You email reports to the following people:
Workers in your organization who have a specific job title
You can use the @<Job Title>@ token to email reports to workers in your organization who have a specific job title. For example, suppose that you want to email the Recruitment Projects report to all workers in your organization who have the job title of Staffing Specialist. In this scenario, you would enter the @Staffing Specialist@ token in the To field when you email the report.
The @Staffing Specialist@ token instructs Microsoft Dynamics AX to perform the following tasks:
Retrieve a list of all workers who have the Staffing Specialist job title.
Retrieve the primary email address for each worker who is identified in step 1.
Email the Recruitment Projects report to each worker who is identified in step 1 by using the email addresses that are retrieved in step 2.
Customers and vendors who have a specific purpose
You can email reports to customers and vendors who have a specific purpose by using the @<Purpose>@ token. In Microsoft Dynamics AX, contact information (such as email addresses) for customers and vendors has a purpose associated with it. For example, a customer may have an email address where the purpose is Billing and another email address where the purpose is Delivery. Now suppose that you want to email a sales order to a customer. In this scenario, you would enter the following token in the To field when emailing the sales order: @Billing@
The @Billing@ token instructs Microsoft Dynamics AX to perform the following tasks:
Identify the customer that this sales order must be sent to.
Retrieve a list of email addresses for the customer that have the Billing purpose.
Send the sales order to the customer by using the email addresses that are retrieved in step 2.
For more information about how to insert tokens when you send a report as email, see Print or email a report.
Developers can customize the functionality of the tokens by using the SysExtension framework. For example, you can develop an additional customization to retrieve titles from an external address book and send a report to the list of addresses that is retrieved externally.
You can also customize tokens to specify other print destinations by using print management. For example, you can use tokens to specify a printer based on location. In this scenario, a token such as @wh printer@ can be used to specify a warehouse printer.
For more information about how to extend tokens, see Customizing tokens for emailing and printing reports.

 

Ref: http://technet.microsoft.com/EN-US/library/f09d8fb3-b3eb-48e2-9285-22217a06037c.aspx

 
Leave a comment

Posted by on November 11, 2013 in AX

 

Tags: , , ,

Compile Whole AX Code in less than 30 min AX 2012 R2

Hi All,

With the release of cumulative update 7 for Microsoft Dynamics AX 2012 R2, Microsoft has launched a new command line tool to compile the complete X++ code. This tool has reduced the compilation time and 13 times faster. It can compile the whole AX in 30 mins.

For further details,

http://msdn.microsoft.com/library/d6da631b-6a9d-42c0-9ffe-26c5bfb488e3.aspx

 
Leave a comment

Posted by on November 10, 2013 in AX, Basics, X++

 

Tags: , , , ,

Image

Using table method on Document Handling generation via COM

Hi Guys,

I just got a chance to work on creating document using word or excel template. in Dynamics AX we have a very good feature in document handling Create Word document via COM or Create Microsoft Office Excel worksheet via COM. Using these features we can create word or excel template, and create and attached the document to the record filling the template fields from the table record.

I don’t want to explain how to setup this type of document, you can read the blow link for that,

http://technet.microsoft.com/EN-US/library/aa548928.aspx

The problem arises when i try to use the the field which is not on the table or don’t have a direct relation with the table i have setup. For example, i have used the SMAServiceOrderTable and i have requirement to fill the “Payment term” on the template, which is on the ProjInvoiceTable. Which has a relation with SMAServiceOrderTable through ProjTable (SMAServiceOrderTable->ProjTabe->ProjInvoiceTable).

The solution i think for this problem is to customize Document handling feature to have the provision of using the method of the table instead of just the fields.

So the problem solved, I added a field on the “DocuField” table for methodName modify some classes. I have provided the link for the XPO for that.

XPO,

https://docs.google.com/file/d/0B7b9JMHh3V2eYnpaSldVNTg0TFE/edit?usp=sharing

I have modified the DocuField table so that method name of the table can be specified.

Then i make changes on the \Classes\DocuActionTrans\insertField  method, to get the value from method using DictTable class.
Thanks for Reading.

 

Tags: , , , , ,

How to resolve India Tax information error

In AX 2009 India GLS, the tax information does not flow from project details to the transaction while posting service order line and we get errors like,

Field STC number must be filled in.

Field Registration number must be filled in.

After debugging the code I found that the code is missing in following path,

\Classes\SMAServiceFunctionLine_Transfer\createProjJournalLine_Hour

\Classes\SMAServiceFunctionLine_Transfer\createProjJournalLine_ItemConsum

Following code can be written in the above two methods to avoid the errors.

                       //<Zeeshan in createProjJournalLine_Hour  method>

                       projJournalTransHour.initFromProjTable_IN(ProjTable::find(serviceOrderTable.ProjId));                       

                       //</Zeeshan>

                   //<Zeeshan in createProjJournalLine_ItemConsum  method>

                   inventJournalTransItem.initFromProjTable_IN(ProjTable::find(serviceOrderTable.ProjId));

                    //</Zeeshan>

This code resolves the tax information flow from project to transactions issue.

 
Leave a comment

Posted by on June 23, 2013 in AX, Dynamics, X++

 

Tags:

2011 in review

The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.

Here’s an excerpt:

A New York City subway train holds 1,200 people. This blog was viewed about 5,200 times in 2011. If it were a NYC subway train, it would take about 4 trips to carry that many people.

Click here to see the complete report.

 
Leave a comment

Posted by on January 2, 2012 in AX

 

Dynamics AX2012 Fact boxes

Fact boxes in Dynamics AX2012 is another very pretty feature. Before writing anything see the below screenshot of the Customer Listpage.

The area in the red box are the fact boxes, which are new in AX2012. These fact boxes provides extra information of the selected record for example the related information fact box shows the quotation, invoices of the customer selected. By this feature user don’t need to move to other form to get the information. User can get the summarized view of extra information in the fact boxes.

On AOT, there is a new node called “Part”, which holds the fact box objects. The available type of fact boxes are,

  • Form part
  • Info part
  • Cue part
I will provide more detail about how to develop fact boxes and place it to any form. Fact boxes can be placed on on listpage or forms.
Wait for my new post to know more about fact boxes. Keep reading my posts.
 

Tags: , , , , , , , , , , ,

Different styles of Tabs in AX 2012

User Experience in Dynamics AX 2012 has really been improved and we have some more stylish way of designing the form. In AX 2012 the tabs are now can have different styles. In 2009 we have Tabs displayed in horizontal, see the below image.



This style is still available in AX2012. Now, take a look other styles of tab in AX2012

 

 

Fast Tabs

Fast tab is a new style of tabs, in this style the tabs can be expanded and collapsed. This style is useful if user wants to view the information from two or more tabs at the same time.

 

Vertical Tabs

In vertical tab style, the tabs are displayed vertically on left side. This style can be used in parameters form of modules.

Index Tab

Index tabs are used for line details information. The tabs are displayed at the bottom of the form/group. See the below screen shot.

So the tabs are now more stylish in AX2012. But how can we change the style? It looks that we need to a lot of work. However, believe me it is a piece of cake. The styles can be change by just setting the “Style”  property of Tab.

Isn’t it simple? Keep reading and visiting my blog and wait for more interesting things of AX2012.

 
Leave a comment

Posted by on August 18, 2011 in AX, Dynamics, Forms, Microsoft

 

Tags: , , , ,

Dynamics AX 2012 EP Session video

Enterprise Portal is one of the most attractive feature of Dynamics AX 2012. Enterprise Portal for Microsoft Dynamics AX provides a Web-based application framework that allows for users to interact with data in Microsoft Dynamics AX through a Web browser.
I shared this video to have the understanding of the development of EP in AX 2012.

see the video by clicking the below link.

http://vimeo.com/26902748

 

Thanks & Regards.

 

 

Tags: , , , , , ,

Dynamics AX EP Session

Hello Guys,

I have presented a session on the Dynamics AX Enterprise Portal. See the attached presentation. I will share the video of the session very soon.

Keep reading and visiting the blog.

Share What you have learned – EP

 

 

Tags: , , ,

Delete Action

Cascade

A cascading delete action will delete all records in the related table, where the foreign key is equivalent to the primary key of the current table. That is, deleting the parent record will also delete the child record(s) in the related table. This cascading will take place whether the deletion is performed in code or directly by a user through the user interface.

Restricted

A restricting delete action will raise an error message if the user tries to delete a record, where records exist in the related table where the foreign key is equivalent to the primary key of the current table. This error will only appear if the deletion is performed through the user interface. A deletion from X++ code will be allowed to proceed and will not be cascaded to the related table. In this case the programmer should call .validateDelete() themselves prior to the call to .delete()

Cascade + Restricted

The delete action performs a restricted, if the record of the table will be deleted directly and performs a cascade, if the record of the table will be deleted through a cascade delete action of a other table.

 

Thanks for reading. keep visiting and giving feedback.

 
Leave a comment

Posted by on February 7, 2011 in AX, Basics, X++

 

Tags: , , , ,