strfmt | rust library for formatting dynamic strings | Code Quality library

I can reproduce the issue.

It seems you have a knack for finding those little idiosynchracies in x++. To answer your questions, yes, this could be an issue in the compiler. As I said in a comment on one of your other questions, x++ has some legacy baggage from the time when it wasn't part of the .NET language family. In general, I consider compilation during save of a single object or even the compilation of a whole project/solution more of a nice to have. The only compilation that in my experience works reliably and produces a useful result is the compilation of the complete package/model (in Visual Studio, it is the one called by the Dynamics 365 > Build models... menu).

I don't think the issue you describe is a known issue. At least I wasn't aware of it and I don't know of a fix for it. And no, I don't think there is something wrong with the code. If it compiles successfully with the "Build models..." compilation, it should be good to go.

This page of AX 2012 documentation is still relevant (I cannot find a AX365 version). Highlighting the important bit gives:

The rules for creating query range value expressions are:

• Enclose the whole expression in parentheses.
• Enclose all subexpressions in parentheses.
• Use the relational and logical operators available in X++.
• Only use field names from the range's data source.
• Use the dataSource.field notation for fields from other data sources in the query.

This means that X++ expects curly brackets around every comparison operator (a.k.a. "subexpression" in the documentation). You are missing some...

Also, use the date2strxpp() function to properly handle all date to string conversions. This function can handle empty date values (dateNull()) by translating these to 1900-01-01. I doubt that putting an empty string (SysQuery::valueEmptyString()) in there will work.

So try this, the commented subexpression levels show the bracket groupings:

The error is clear. You can't do crossCompany and updates in the same select query. Method 2 below is closer to what you're doing. When updating parameter tables, it can be done a few ways because of the Key on the table.

See below:

Try changing your code to the below. I don't have the same dimension that you have, so you might need to tweak it.

Please check below one of the possible examples with regular expressions:

The closest thing you could do is:

The error is straight forward.

Error The augmented class 'PurchTable' provides a method by this name, but this method cannot be used as a chain of command method since the parameter profile does not match the original method.

Take a look at the highlighted parameter profile and compare to yours.

Edit: Take a look at these links for more info on Chain of Command (CoC):

• https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc
• https://channel9.msdn.com/Blogs/mfp/X-Chain-Of-Command (This video is excellent)

There are several ways, you can try something like this:

Example, in class A define and set boolean variable, in class B pass the boolean variable and use your logic.

Code example:

Class A