Errata

The sentence twice splits the word "stepping" into "step ping".

"You can open these files in Visual Studio to set breakpoints and perform common tasks, such as step ping into and step ping over."

The last sentence of the Namespace bullet point refers to an example, but there are no examples being used.

"Namespace Optionally, you can specify the XML namespace that should be used in the WSDL. If the XML namespace isn't specified, http://tempuri.org is used by default. This example uses the namespace http://schemas.contoso.com/axbook/2012/services."

The last sentence, referring to an example, should be deleted.

A comma is misplaced.

"Instead of each security role being defined individually, in a security role, hierarchy security roles can inherit the permissions from other security roles and reuse them."

The second comma should be moved to the right by one word, so that it comes after the word hierarchy ...

"Instead of each security role being defined individually, in a security role hierarchy, security roles can inherit the permissions from other security roles and reuse them."

The word order "a using" should be reversed, to "using a".

-----
... or when a using prebuilt component would save time ...
-----

Looks like two different ways of phrasing it were considered and accidentally mixed:

"This will require that you to optimize the queries used to load the list page."

Should be either:

1) "This will require that you optimize the queries used to load the list page."

2) "This will require you to optimize the queries used to load the list page."

Note from the Author or Editor:
"This will require that you optimize the queries used to load the list page." is correct.

The word "the" is missing:

"The navigation layer consists of top-level pages that serve as a starting point for [THE] user as he or she ..."

The word 'immediately' is misspelled as "mmediately".

"You must define all fields, however, on the selection table model element, and only one selection table is allowed mmediately after the from keyword."

Note from the Author or Editor:
On page 99, please change "mmediately" to "immediately."

Offending sentence is as follows:

"You must define all fields, however, on the selection table model element, and only one selection table is allowed mmediately after the from keyword."

The name of the function is putToDialog(), but the sentence just above the code calls it putFromDialog().

"The overridden putFromDialog [<- should be putToDialog] method transfers the contents of operation input parameters to dialog box controls."

Text is missing in the sentence that starts with "Use this development Environment" , right after "Microsoft .Net plug-ins for".
I think "for" is in the wrong place.

Note from the Author or Editor:
On page 7, in the description for the Visual Studio bullet, please change the sentence that follows to:

Use this development environment to develop Microsoft .NET plug-ins and extensions for Microsoft Dynamics AX clients, servers, and services; to develop for Enterprise
Portal, and to develop SSRS reports.

Typo.

"A setting of 0 means that HERE is no timeout."

should be:

"A setting of 0 means that THERE is no timeout."

Note from the Author or Editor:
In the third bullet point at the beginning of page 463, please change the word "here" to "there."

That numeric value (45) for timeout in the paragraph does not match the numeric value (15) in the XML ...

"... to set the maximum number of cached concurrent sessions to 300 and the session timeout to 45 seconds ...

<Microsoft.Dynamics>
<Session MaxSessions="300" Timeout="15" />
</Microsoft.Dynamics>"

Note from the Author or Editor:
In the first code example on page 223, please change

Timeout="15" />

To

Timeout="45" />

An invalid acronym ("AOD") is used (it should be "AOT" instead).

"Set the ... to the display menu item that corresponds to the details page, and then refresh the AOD."

Note from the Author or Editor:
On page 218, in step 10 of the procedure, please change "AOD" to "AOT."

The first sentence of the last paragraph uses back-to-back redundant words ("because since").

"... if you need to use aggregation and group by in queries, because since the update_recordset .."

Note from the Author or Editor:
On page 442, in first sentence of the last paragraph, please remove the word "since."

The X++ SQL command "select" is misspelled as "elect".

There are 2 select commands in the X++ code: it is the second one, which is not part of the insert_recordset command but is instead a standalone SELECT, that is the middle statement in the following ...

ttsCommit;
elect count(RecId) from insertInventTableInventSum;
info(int642str(insertInventTableInventSum.RecId));

Note from the Author or Editor:
At the end of the first code block on page 429, please change "elect" to "select" as follows:

select count(RecId) from insertInventTableInventSum;
info(int642str(insertInventTableInventSum.RecId));

Minor typo. The first sentence of the 3rd paragraph has near its end, "... of a custom service was discussed in a previous example ..."

There is more than one way to correct it; one way would be to add the word "that":

"... of a custom service THAT was discussed in a previous example ..."

Note from the Author or Editor:
In the first sentence of the third paragraph of page 410, please add the word "that" after "of a custom service," as the customer suggests.

There is a missing period between two sentences.

"You can specify a startup project in the Options form [<-period needs to go here] If specified, the chosen project automatically opens when Microsoft Dynamics AX is started."

Note from the Author or Editor:
On page 27, in the last paragraph on the page, please add a missing period as follows:

You can specify a startup project in the Options form [<-period needs to go here] If specified, the chosen project automatically opens when Microsoft Dynamics AX is started.

The last sentence duplicates the word "the", resulting in "the the":

"Locking the form can also improve performance because the the form is redrawn only once."

Note from the Author or Editor:
On page 174, in the last sentence of the "Runtime modifications" section, please remove the repeated word "the."

Offending sentence:
Locking the form can also improve performance because the the form is redrawn only once.

The third sentence in the Unit of Work paragraph begins, "This is can be troublesome ..."

Note from the Author or Editor:
In the Unit of Work section on page 167, please change the third sentence from "This is can be troublesome" to "This can be troublesome."

The text states, "4. ... The CSR clicks the Sales tab of the Action pane and clicks the new Sale Quotation button.", but the referred to figure (Figure 5-8) does not have a Sales tab on the Action pane, and the circled 4 in the figure is on the Customer tab of the Action pane.

Note from the Author or Editor:
In Step 4 on page 147, please change "Sales tab" to "Sell tab."

In Figure 5-8, please move the "4" so that it is above the Sell tab. It is currently above the Customers button.

The text states "The steps in this scenario correspond to the numbered items in Figure 5-9 ..." - it should refer to Figure 5-8 instead.

Note from the Author or Editor:
In the last paragraph on page 146, please change "Figure 5-9" to "Figure 5-8."

Figure 2-36 "The Syncronization Log dialog box" has sneaked its way into the "Show the history of an element" section. It should have been in the previous section; "View the synchronozation log".

Note from the Author or Editor:
Please move Figure 2-36 and its caption from page 69 to immediately after the second-to-last paragraph on page 68. That paragraph contains a reference to Figure 2-36.

Below table 2-9 "Version control tasks" theres is the following caption which makes no sense: "Figure 2-34 show the Check In dialog box"

Note from the Author or Editor:
Please move the line "Figure 2-34 shows the Check In dialog box." from immediately below the table on page 66, to immediately before Figure 2-34 on page 67.

The book says: "Updating the Cross-Reference tool also compiles the entire AOS because the compiler emits cross-reference tool".

But in AX 2012 R2 you can update the cross reference in batch IL mode with the xRefUpdateIL class. This doesn't compile any code, since compilation requires a client to be running.

So is it not true that there actually is a way to update the cross-reference on already compiled code, without having to wait for the code base to be compiled as well?

Note from the Author or Editor:
In the Tip section on page 60, please change "cross-Reference" to "cross-reference." The other instances of "Cross-Reference" refer to a particular tool and should remain title capped.

Figure 2-25 "Search results in the Find tool" has sneaked its way into the Compare tool section. It should be in the section before Compare tool, which is Find tool.

Note from the Author or Editor:
Please move Figure 2-25 and its caption from page 55 to immediately before the last paragraph in the "Find tool" section on page 54. There is a reference to Figure 2-25 in the next to last paragraph in the section. The figure should gto after that.