Create an LCS tool that will build a Tier1 development environment from a sandbox.
The process of refreshing a sandbox > executing post refresh activities to activate users etc > exporting a bacpac > downloading the bacpac to a suitable tier 1 environment > converting the bacpac to a bak for MSFT SQL > and enabling the database for use in the tier1 environment for debugging is ...
Enhance Environment Manager Role
The Environment Manager Role can see all the passwords and stop and start all environment in LCS, a granual control mechanism is required so this permission can be assigned and environment level to individual users or groups of users.
Open environment dashboard in new tab
When navigating to a project in LCS, you get to see a list of all the environments available in that project. For easy and fast maintenance it helps if you can open several environment dashboards in the same browser window. Currently, when right-clicking the environment, there is no option to ...
LCS export tier 2 data to asset library in BAK format
We have developers and analysts who have local VMs as well as tier 1 cloud environments we would like to regularly refresh with Production data. The current process is lengthy and cumbersome, and makes it impossible to be pro-active when trying to investigate urgent issues in Production. 1) re...
Thank you for your feedback.
We are not considering the suggestion at this time due to the following reason: Azure SQL platform only supports exporting a database schema and data in the .bacpac format. Traditional .BAK format is not available. To quickly troubleshoot data from PROD, you can use the documentation here:
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/database/dbmovement-scenario-debugdiag
Ability to schedule self service features in Lifecycle Services
Currently the only way to execute self service features in LCS is on demand, e.g. Maintain>Move database. Given that most maintenance operations need to happen out of hours, I think it would be very useful to be able to schedule them instead of having to wait for them to run interactively. ...
This has been released - please see below documentation:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/dbmovement-operations
Build compare tool for proactive quality updates
With the introduction of proactive quality updates, it has become even more important to understand what is added between Microsoft platform and application builds. One suggestion was to sign up for Community Driven Engineering (CDE), however this requires a CxO sponsor and was originally inte...
Export Production db to Tier1 environment
To debug a Live issue from production it takes around 24 hours to replicate and copy database to development environment. user need to perform below steps - Refresh from production - Purge/Truncate tables script in sandbox using JIT - Export database to Asset Library from Sandbox - Convert datab...
Regression Suite Automation Tool - run without overwriting test case steps
When running a test case on Regression Suite Automation Tool, the associated test case in DevOps has its steps overwritten. Currently we are not using BPM or LCS for test cases, but are attaching the Task Recorder's recording.xml to test case in DevOps. The test cases were written in DevOps wi...
"Merge"assets as versions
Following those two ideas:
- "Upload a new version" in project asset Library
Thank you for your feedback.
We are not considering the suggestion at this time due to the following reason:
It is now possible to delete assets in the project asset library that have been previously deployed. We recommend doing all package generation in Azure DevOps.
Sincerely,
Lane,
Microsoft.
"Upload a new version" in project asset library
In shared asset Library, there is an option to upload a new version of an asset. This option is not available in the project asset library.
For example, with nightbuilds, we have a tons of entries which polute the view and prevent getting the releases. Also, it's definitelly a...
We are not considering the suggestion at this time due to the following reason:
It is now possible to delete assets from the project asset library for those that were applied to your environments. We recommend versioning your assets in Azure DevOps and using the traceability there between package version -> build -> deliverables and features.
Sincerely,
Lane,
Microsoft.
Administrator
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
PM,
Microsoft.