-
LCS Dynamics should reflect the proper VM name
If you deploy both the build and dev machines into a single environment, the Login dropdown does not show which application you're about start. It should reflect the VM name in the selection option value.
-
An option to automatically shutdown newly deployed virtual machines
At the moment LCS does not have a fixed duration for deploying new Operations environment virtual machines, aka. we don't exactly know how long it takes. An option in the deployment settings to enable shutting down the machine(s) when they are deployed would be beneficial cost wise.
-
ODATA: Enable DateTime filtering on extended data entities
If you add fields to data entities using extensions (including the staging table), you can't use $filter function in the oData API. Using a filter of e.g.
/data/Customers?$filter=MyCreatedDateTime gt 2017-01-01T00:00:00Z
results in an error of"An error has occurred. The type 'System.DateTimeOffset' for the query operator is not Queryable!"
-
Support for CodeLens
The development experience of Dynamics 365 for Finance and Operations is lacking a couple of features that are available in other .Net languages.
One of the most beneficial tool missing is CodeLens.
"Stay focused on your work while you find out what happened to your code - without leaving the editor. Find references and changes to your code, linked bugs, work items, code reviews, and unit tests. "