Dynamics 365 FO / AX - thoughts on application development and customizations

 A good and often used trick to use when hunting down bugs is putting a break point in the info class in the method add() and examining the call stack when an error is thrown causing the add method in the info class to be called for updating the infolog. However sometimes when you are debugging in Visual Studio the debugger will not load the symbols needed to debug in the info class. In the old days you had to resort to the very slow "Load all modules, unless excluded" under Debugging / Symbols / Automatic symbol loading preference, which would load symbols for ALL modules. A neat addition that Microsoft has added to the Dynamics 365 FO/SCM extension for Visual Studio (can't remember from what version at the moment), is that you can now debug with "Load only specified modules". So when you encouter that the debugger will not load symbols for the info class do this: 1. Choose Options in the 365 Visual Studio extension 2. Go to Dynamics 365 / Debugging 3. Put a ch...

Preamble: This occurred running on Finance and Operations (Dynamics 365) - (Platform Update57) 7.0.6861.86 extension for Visual Studio. Historically the x++ langauge has not had great support for access modifiers. The original workings was, that all class members in a class were private, and could not be accessed, by code outside the class, unless ofcourse you made a (parm) method giving access to change or just get something. Methods could have access modifiers but they were seldom used and were always public, unless you explicitly wrote something else. Somewhere a long the lines in D365 x++ has evolved to be more c#-like and therefor you can now put access modifiers on you class members, so that if you declare a class member public, you do not actually need to write an access (parm) method. However, the x++ compiler has it's quirks it seems. Consider this class declaration: internal final class MOLSOPackingSlipFromReceivedTransitGoodsUpdater {    ...

 Working in the WHS module a customer needed to be able to change the transport provider (carrier) and the provided service (carrier service) directly on the Shipment chosen in the pack form. This presents some interesting challenges, working within the limits of the extension mechanisms in D365. Firstly as of time of writing the application implements a table relation on the WHSShipment table to the table TMSCarrierService (transport service codes provided by a carrier). It does so by having a Normal field relation between TMSCarrierService.CarrierServiceCode and WHSShipmenttable.CarrierServiceCode, thus NOT taking in to consideration the Carrier that have been chosen on the shipment. Trouble is that you can not change a table relation using extensions, AND you can not using extensions to introduce a new (correct) relation that overrides the existing one. So instead of just changing the table relation (if that was possible and simple), I needed to do 4 extensions. 1) A new class w...

" When ISV solutions are installed as binary only, the current development tools does not support displaying delegate methods, and there are no interaction to copy the enventhandler method. Please add the Option to see the class in design view and from here se and copy event handler methods, Or display them directly from the Application explorer and make the interaction here. " Please vote: https://experience.dynamics.com/ideas/idea/?ideaid=a5d9dd10-a651-ec11-a3ee-0003ff459fb2

I was tasked with developing a custom "process" for printing ad hoc labels in the Dynamics 365SCM WHS app. WHS process guide - development docs Reading the great articles from 1clickfactory (starting point  https://www.1clickfactory.com/blog/advanced-whs-mobile-device-development-part-1-process-guide-framework/) gives a good starting point. Especially Edgaras' tip on running  SysExtensionCache::clearAllScopes();  in a runnable class after introducing a new step/pagebuilder class combination  is VERY useful. And of course Microsoft's own documentation ( https://docs.microsoft.com/en-us/dynamics365/supply-chain/warehousing/process-guide-framework ) also helps. However, I wanted to chip in with a couple of things. Extending WHS base enums If you extend the WHSActivity, WHSWorkExecuteMode or WHSWorktransType base enums with new options it is a good idea to run a database synchronization when you are done with extending them. Otherwise you might be frustrated to find, th...

Supressing the infolog is often useful in D365FO when augmenting code. When augmenting code using COC (Chain Of Command), you can have new code run either before or after the code you are augmenting. This means that any infolog-messages that the standard application code does, will be shown to the user, even if your augmentation supports a scenario where there must be no infolog-messages. How do you avoid the standard application infolog-messages ? To the rescue comes temporary supression of the infolog. The suppression consists of: 1) Saving the current infologLevel 2) Setting the infologLevel to SysInfologLevel::None 3) Run your code 4) Restoring the saved infologLevel to the infolog For example a table could have a validatewrite-method that validates that you are only allowed to use 3 out of 6 options in an enum-field, and you need to allow for a fourth one. Table a - validateWrite method: boolean validateWrite() {     Switch (this.enumField)     {     ...

 Note to self. Be careful of creating extensions to a table, that contains no augmentation. I experience problems when opening the Released Products Forms on my developer box. I got a run-time error " Object reference not set to an instance of an object"  when opening the form. The error also occurred when changing records in the form, BUT strangely enough ONLY the first time the cursor arrived a at record. The second there was no problem.  Researching a bit with the debugger, I could see that the error occurred at the super() call in the FormRun class, and in the active method on the EcoResProduct datasource. I discovered that I by accident had created an extension to the table EcoResProduct that contained NO augmentation what so ever. Double checking that the extension had not been checked in to azure DEVOPS, and that the xml-file for the table extension in  K:\AosService\PackagesLocalDirectory\xxxxxDev\xxxxxDev\AxTableExtension contained no augmentation, I deleted...

WHY oh WHY, does the developer-box not tell you, that you can not use custom code in an SSRS-report ? Working with a SSRS-report on Dynamics 365 FO, I came across the following annoyance, with Microsofts setup virtual boxes in Azure. I was working with getting the report to present the filters and chosen parameters from the report dialog that the user is running the report with. At some stage, I thought making a function with custom code in the report properties, was the way to go, but I abandoned that approach in favour of another - AND forgot all about the code. This meant that the custom coded was checked into dev.azure.com, and included in the build on the build box. So I got the deployable package and uploaded it into asset library in LCS, and applied to the SAT-environment. No worries. Right until the users started tested the report in the SAT-environment, because they got: So this meant going back to the dev-box, cleaning out the custom code, doing the building and appl...

I have used a bit of time this morning trying to figure out how to change the query in an RDP based SSRS report. I needed to change the report from using a query JmgPaySpecification to using the query JmgPaySpecificationExt instead. I started out by changing the     SRSReportQueryAttribute(queryStr(JmgPaySpecificationExt)) attribute in the classdeclaration of the RDP class and compiling it. Then I went to Visual Studio, opened the report and doing a rebuild on it to get it refreshed in the AOT. However that didn't seem to change anything, and doing a find on the SSRS-report searching all nodes and searching for JmgPaySpecification revealed: So doing the above changed nothing. The solution is, to go into Visual Studio opening the report: 1. Go to Datasets and highlight the Dataset 2. Change the Data Source Type from Report Data Provider type to Query.     This clears the Query setup. 3. Change the Data source Type back to Report Da...

When documenting test or setup it is advantageous to show as many values in the status bar as possible (especially the AOS name and company accounts id and maybe date and time), to be able to show in screen dumps what environment you are using. Here is a quick little job for setting up ALL fields to be shown in the status bar. Dynamics AX 2009: static void Job130(Args _args) {     #LOCALMACRO.FLAG_StatusLineHelpText             (1 << 0) #ENDMACRO     #LOCALMACRO.FLAG_StatuslineDatabase             (1 << 1) #ENDMACRO     #LOCALMACRO.FLAG_StatuslineWatch                (1 << 2) #ENDMACRO     #LOCALMACRO.FLAG_StatuslineNumLock              (1 << 3) #ENDMACRO     #LOCALMACRO.FLAG_StatuslineCapsLock             (1 << 4) #ENDMACRO   ...

Here's how to get graphics stored in AOT as a ressource onto a report in Dynamics AX 2009. Do a display method with: display Bitmap  companyLogo() {     return SysResource::getResourceNodeData(SysResource::getResourceNode(identifierstr('zabel_JPG'))); } where zabel_jpg is the graphics file stored in ressources in the AOT. Drag the method onto the design.

Tasked with hiding a specific field on the salesLine table in the sales order forms depending on the value of a field on SalesTable I searched for methods and came across: https://community.dynamics.com/ax/f/33/t/168729 I agree with the method of finding the field on the datasource of the formpart however a better method of making the field invisible is to reference formDataSource.object(fieldnum( , )).visible(true/false); instead of actually having to reference the form control. This will make the field visible/invisble anywhere in the form that the field of the datasource is used. In my case it was done like this: private void toggleintraCodeReturn() {     PartList    pl;     int pCount,partdsCount;     FormRun part;     boolean shown;     FormDataSource pfds;     FormDataSource  fds,partfds;     shown = this.currentSalesTable().CustMaterial == NoYes::Yes;     if (this.c...

Just finished an assignment making a tool for Dynamics AX 2012R2 for creating project quotations in word, using AX data. The customer is an ETO company manufacturing production lines for slaugtherhouses. The tool should create a quotation file word document (.docx) using a word template (.dotx) prepared in a certain language. This would allow the customer to design the layout of the document in a easy and familiar way. The spec required the quotation to include Budgets with detailed information for each sub project of a main project. Budgets summarized for each sub project of a main project. Scope of supply, which contains short technical descriptions of the included units on the production lines (sub projects) Technical descriptions - a section of the document containing listing (only once for each unit/sub project) complete descriptions with pictures of each included unit The algorithm in short is this: Now the challenge was that for most itemids in the item forecast ...

Before Dynamics AX 2012 and the new editor which makes things a bit more Visual Studio like, we had some features in the AOT, that are gone now but I miss. I *might* have rambled and raved about this before ( http://gotdax.blogspot.dk/2012/03/dynamics-ax-2012-annoyances-for-old.html ) ;-). E.g. I miss the ability to mark all fields on a table in the AOT and simply copy them to code. In the olds days this could be done by simply marking the fields in AOT and dragging them to the editor window. I needed this and got fed up with having to type the field names my self so I made a little class with the main method: public static void main(Args _args) {     #AOT     DictTable   dt;     DictField   df;     int f,start,end;     Set s;     SetEnumerator se;     int tableno;     TextBuffer txtb = new TextBuffer();     str fi...

Once a long time ago I found an interesting document on the inter web, describing different calendar systems. From that I made a php-class for my website that can calculate easter sunday in the gregorian calendar. Then it is easy to calculate the rest of the danish holidays as they are offset according to easter sunday (except of course those that have a fixed date). I translated that class in to x++. You can find it here: https://onedrive.live.com/redir?resid=9B63D38F981FFD1B!39710&authkey=!ABv0yYPULV3ReIE&ithint=file%2cxpo Today I got talking with a colleague about calculating easter sunday so he mentioned that he had also made a version of the calculation: http://stackoverflow.com/questions/11048524/how-to-calculate-easter-sunday-in-x So of course - being a bit nerdy - we just *had* to check if the routines arrived at the same result. So we came up with: static void EasterTest(Args _args) {     Yr x;     date easter(Yr ...