I would like
to share a very good searching tool (fileseek) that I am using for search the
data in my Dynamics AX enlistment, you can find more detail using the link http://www.fileseek.ca/. This tool can be
used a replacement of the cross reference functionality in AX, but you should
have the enlistment for that particular branch
name is Arsalan Gulzar and the intent to create this blog is to discuss the problems and issues that developer face in the dynamics AX development and to share the new things that come up with the new version of AX.
Wednesday, April 4, 2012
some Dynamics Axapta FAQs
1 . Breakpoint in
clicked method
There is quite well known bug in AX that breakpoint placed in the clicked() method of a button will not be triggered. It is quite unpleasant one since when one faces it first time he gets totally confused. However, there are easy workarounds for this bug. First one – put breakpoint into the method that is called from clicked (in most cases it is possible). But if not, keyword breakpoint can be used – it will be triggered in clicked() method.
There is quite well known bug in AX that breakpoint placed in the clicked() method of a button will not be triggered. It is quite unpleasant one since when one faces it first time he gets totally confused. However, there are easy workarounds for this bug. First one – put breakpoint into the method that is called from clicked (in most cases it is possible). But if not, keyword breakpoint can be used – it will be triggered in clicked() method.
2. Global::isType
The easiest way
to determine if an EDT extends another EDT (not necessarily directly) is to use
Global::isType() method.
For example:
For example:
isType(extendedtypenum(PurchUnit),
extendedtypenum(UnitIDBase));
give true, since PurchUnit extends UnitID, which extends UnitIDBase.
give true, since PurchUnit extends UnitID, which extends UnitIDBase.
isType(extendedtypenum(ABCModelType),
extendedtypenum(NoYesId));
gives false, since ABCModelType and NoYesId are in different hierarchies.
gives false, since ABCModelType and NoYesId are in different hierarchies.
3. Delete actions
and multiple relations
If one table has
several relations to another table delete action will not work properly. In
such case delete action will be triggered for only one of the relations. So, in
the case of multiple relations one should write his own cascading or
restricting logic in the delete method. An example can be found in Unit and
UnitConvert tables. UnitConvert table has two relations to the Unit table –
from unit and to unit. Table Unit has cascading delete action for the
UnitConvert table. However, if a unit will be deleted, only unit conversions
with from unit equal to the deleted one will be deleted. Conversions with to
unit equal to the deleted one will survive. Example of correct implementation
can be found in InventTestEmplResponsible and EmplTable. EmplTable has delete
method overridden to perform manual delete in the InventTestEmplResponsible
table.
SSAS – OLAP – SSRS Report using OLAP
I have created a presentation regarding the SSAS and OLAP in Dynamics AX
Feel free to contact me for any questions.
·
SSAS
o
OLAP
§
Cube
·
Measure
·
Dimensions
§
Perspective
o
BIDS
o
MDX Queries
o
Reports
§
KPI
§
Miscellaneous
Feel free to contact me for any questions.
Subscribe to:
Posts (Atom)