Overview of Dynamics AX build numbers

-
http://blogs.msdn.com/b/emeadaxsupport/archive/2009/07/01/overview-ax-kernel-build-numbers.aspx

Comments

Post a Comment

Popular posts from this blog

Execute and access code restricted internals as a partner or customer

-
Image
It's possible to bypass the internal access modifier that is used to protected code in Dynamics 365 for Finance and Operations from being executed by partner or customer code. This is possible since the standard models that is provided by MS in each release contain a Descriptor file that haven't been clean up and still contain a list of model names under InternalsVisisbleTo . All models that are listed under InternalsVisibleTo can reference/call code that has been marked as internal. See for example: K:\AosService\PackagesLocalDirectory\ApplicationSuite\Descriptor\Foundation.xml Most of the models listed under the tag InternalsVisisbleTo are unit testing models that are not shipped with the release. This makes it possible for a partner or customer to create a model with the same reference name and that way gain access to executing any code that should only be accessible by your core MS models. Since you have test models for most of your models this give...
Read more

Expressions in query ranges

-
When creating expressions with comparisons to strings you might have to surround the string with " " like in the example below. queryRange = strFmt('((%1 == \"%2\") || (%3 == \"%4\"))', fieldStr(ProjTable, Responsible), queryValue(element.getEPProjWebApp().EPProjUser().emplId()), fieldStr(ProjTable, ResponsibleFinancial), queryValue(element.getEPProjWebApp().EPProjUser().emplId())); It's important to use \" to achieve the correct behavior. Read more about ranges here
Read more

Removing duplicate records

-
When you make a change in the layers of AX you will be faced with the installtion checklist. I some cases a removal of a layer might cause duplicates of records that can cause error when trying to synchronize the tables. To solve this problem a removal of the duplicate records is necessary. This can be done with the sql query below: delete from LedgerBalancesDimTrans where exists( select * from LedgerBalancesDimTrans as test_inner where test_inner.dataareaid = LedgerBalancesDimTrans.dataareaid and test_inner.accountnum = LedgerBalancesDimTrans.accountnum and test_inner.transdate =LedgerBalancesDimTrans.transdate and test_inner.periodcode = LedgerBalancesDimTrans.periodcode and test_inner.dimension = LedgerBalancesDimTrans.dimension and test_inner.dimension2_ = LedgerBalancesDimTrans.dimension2_ and test_inner.dimension3_ = LedgerBalancesDimTrans.dimension3_ and test_inner.ledgerbalancesvariant = LedgerBalancesDimTrans.ledgerbalancesvar...
Read more