Allow ehanced extensions & debug directly on binaries (without XPP files)
Because we deliver deployable packages (Bin) to a customer, there is no 'xpp' and no possibilities to make enhanced extension on that. Of course, we want to give the opportunity to our customers to make extensions on our functionalities. But we want to be sure that our code will not be stole b...
XPO Conversion tool for d365fo
It would be great if we may have direct access to the utility that converts AX2012/AX2009 XPO format to the d365fo XML-based format. Or at least having a utility that converts an AX2012 Model to XML-based d365fo artifacts, would also be a great help.
Visual Studio 2019 support
Visual Studio 2017 has a number nice little features that are definitely missed when working in Visual Studio 2015. With the release of Visual Studio 2019 I think that we're due an IDE upgrade to make better use of some of the features released over the last 4+ years.
Allow to set a standard field mandatory
I totally understand we can't modify a standard mandatory field to set it not mandatory anymore. But we need sometime to set a standard field as mandatory regarding the customer's processes. By now, we can't trigger this property on the field. So we have to implement it in the table methods an...
Preview pane like AX 2012
You can see preview pane in many Grids like All sales order, all purchase order In AX 2012 The Preview Panes are a great part if developed in D365 like AX2012 https://www.google.ae/imgres?imgurl=http%3A%2F%2F4.bp.blogspot.com%2F-JcztC4Ky5sY%2FTv462H1dyCI%2FAAAAAAAAAPc%2F3E-5VXqg6kY%2Fs1600%2FL...
Compiler should check adding field to dimension related view (such as DimAttributeOMDepartment)
When we add a field to DimAttributeOMDepartment, standard code, classes\DimensionEnabledType:constructForSystemDefinedByTableId() will be not work. This code expect DimAttributeOMxxxxx view has only three field, Key, Value, Name. But compiler returns any error when adding field to DimAttributeOM...