Mehrdad Ghazvinizadeh Cegeka Solution Architect

Being able to filter the data before sending it to Excel and/or being able to manage the Excel add-in in order to use filters so data volume can be limited before it's sent to/retrieved in Excel. In effect, send the form filters to the Excel Add-in.

Currently there is only one mapping possible between LCS and DevOps work item types. Would be great if we may have different mapping per BPM-tree It makes it more flexible to manage Also having the possibility to provide some default values in the mapping for the fields that are not by default existing in LCS but in DevOps is also very welcome.

The plans about OneVersion for Microsoft Dynamics 365 applications are already announced. While OneVersion is enabling Customers, Microsoft and Partners to respond the ever-changing market and business demands in an agile way using all the hidden possibilities of a modern managed software ecosystem; It is important to ensure the smooth transitions between the frequent periodic and regular (monthly) updates. Therefor the need to have a “hit-map” to show which areas of the application/functionality is affected by each update wave is a big accelerator in this direction. Having the fact that nowadays we have the application usage intelligence based on the collected telemetry data as well as the fact that business processes can be modelled in the Life Cycle services, it should be possible to create such a hit-map, which is even interactive and is tailored to the specifications and usage of a customer environment. This will be a guide for Customers and Partners to know where to start when a periodic update needs to be validated by them before giving the approval for deployment to the Production.

Currently the implementation of Excel formulas within RSAT test case Excel artifacts looks to be very limited when it is about using "Saved variables". It would be great if we may use saved variables in any kind of Excel formulas and not be limited to a given kind of formulas and or given kind of data type. This might off course need refactoring the current implementation. See also support case for related information: 119043025000810 - Excel formula calculation using saved variables ({{global_value_date}} + 2

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.

We see in lots of situation that the "Details transaction" design pattern would be much more user friendly, if we may add a horizontal slider between the two sections of the form. Like what I've illustrated in the figure here: https://ibb.co/jTsbQv5 Is this something that might be considered by the product team? Thanks! See also https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/user-interface/details-transaction-form-pattern

Related to "D365 SCM Inventory Visibility" service and how it works together with D365FO Inventory.

The amount of available inventory in a D365FO system can change in different ways. 

Some of those changes go through the Inventory Visibility (IV) service, which puts in a soft reservation in IV before it's applied in D365FO. 

But there are also other situations where the inventory level in D365FO changes without IV being involved.

Normally, these changes are synced to IV regularly, which means that the inventory level isn't always exactly right between the sync job runs. 

In a system that doesn't have a lot of activity, this isn't a big deal. But in a system that's really busy, it can cause problems, like promising the same stock to multiple customers.

Ideally, we want to be able to see what's happening (like checking how much stuff is available for online orders in FnO, which uses IV) and take action (like making adjustments to the inventory or putting in soft reservations when important things happen, like transfer orders, production orders, or purchase orders).