diff --git a/power-platform/developer/unified-experience/finance-operations-faq.md b/power-platform/developer/unified-experience/finance-operations-faq.md index 1731e08e2b..790e50452c 100644 --- a/power-platform/developer/unified-experience/finance-operations-faq.md +++ b/power-platform/developer/unified-experience/finance-operations-faq.md @@ -58,7 +58,7 @@ If you still need to, try and use [7-Zip](https://www.7-zip.org/download.html) t ### The message "Please wait for update to complete" pop up keeps appearing -When a configuration is created, saved, and the dialog closed, the necessary files are updated and this popup will stop. If the dialog keeps recurring even after you open a new Visual Studio instance, the find the file PackagesLocalDirectory/bin/InstalledVersion.json in reference metadata folder and update the version to match the platform version in your environment. +When a configuration is created, saved, and the dialog closed, the necessary files are updated and this popup will stop. If the dialog keeps recurring even after you open a new Visual Studio instance, the find the file C:\Users\\AppData\Local\Microsoft\Dynamics365\\PackagesLocalDirectory\bin\InstalledVersion.json in reference metadata folder and update the version to match the platform version in your environment. ### Cross reference database validation keeps failing @@ -72,6 +72,7 @@ Ensure that your Microsoft Windows user has access to the specified SQL Server o ```powershell sqllocaldb stop MSSQLLocalDB sqllocaldb delete MSSQLLocalDB +sqllocaldb create MSSQLLocalDB -s ``` 5. Run the new SqlLocalDB.msi (2019) installer. It creates a new MSSQLLocalDB instance. @@ -92,11 +93,7 @@ This result happens when the the unified developer environment isn't ready to se ### What is the earliest version of source environment I can copy from? -Unified developer experience functionality is available for version 10.0.35 and later. Since during copy we also copy compute, if the source environment is earlier than 10.0.35 the target loses unified developer experience functionality. - -### I provisioned an environment from UI, but am unable to run unified developer experience operations - -The UI doesn't provision online environments. Only sandbox and production environments are provisioned via the UI, and unified developer experience operations aren't supported on these environments. Provision OnlineDev environments via the command line, and then run unified developer experience operations. +Unified developer experience functionality is generally available for version 10.0.39 and later. Since during copy we also copy compute, if the source environment is earlier than the target one may lose some unified developer experience features that were made available only in the more recent version. ### Is package deployment of the unit test code required for executing tests in the cloud runtime? @@ -108,7 +105,11 @@ Application Foundation and Test Essentials are required for unit test execution. ### How can I set up a pipeline that automates creation and application of a deployable package to a new environment? -Use the latest version of the Azure DevOps extension from the marketplace. It's now capable of package creation, ISV license addition, and application of the package. Refer to [Dynamics 365 Finance and Operations Tools](https://marketplace.visualstudio.com/items?itemName=Dyn365FinOps.dynamics365-finops-tools). +Use the latest version of the Azure DevOps extension from the marketplace. It's capable of package creation, ISV license addition, and application of the package. Refer to [Dynamics 365 Finance and Operations Tools](https://marketplace.visualstudio.com/items?itemName=Dyn365FinOps.dynamics365-finops-tools). + +### How can I deploy packages received from ISVs to my Unified Developer Environment? + +Place the ISV modules in a common folder and add this common parent folder of all ISV modules to the existing list of reference metadata folders in the active configuration you intend to use. Refer [Install and configure development tools](finance-operations-install-config-tools.md) ### How do I include a license and directly deploy from Visual Studio? @@ -128,7 +129,7 @@ Use **Detach All** to end debugging in place of **Stop Debugging**. ### I applied a package, but it failed. How can I do further debugging to determine the failure? -A link to download operation logs is available in the Visual Studio output pane. It's downloaded if there were failures, or if you enable the setting in **Tools> Options> Power Platform Tools**. +The package deployment could fail in various stages including DB sync, for various reasons including developer bugs. A link to download operation logs is available in the Visual Studio output pane. It's downloaded if there were failures, or if you enable the setting in **Tools> Options> Power Platform Tools**. You can also download the logs from your Dataverse organization: @@ -137,9 +138,9 @@ You can also download the logs from your Dataverse organization: - Select the app and then from left pane, select **Operation History** - Open the respective record by selecting the **Operation Name** and download the operation logs (`operationlogs.zip` file) -### How can I find out what packages are applied to my environment? +### How can I find the history of packages applied, DB sync, and other updates to my environment? -You can check the package applied to your Finance and Operations environment with the following steps: +You can check the packages applied and other updates to your Finance and Operations environment with the following steps: - Login to the Dataverse organization - Find **Finance and Operation Package Manager App** on the main page @@ -148,7 +149,9 @@ You can check the package applied to your Finance and Operations environment wit ### My operation failed, and wasn't able to find sufficient information in the logs. What information do I provide to Microsoft Support? -The correlation ID, client machine name, and timestamp are required for Microsoft to investigate. The correlation ID is in the Visual Studio output pane. Additionally, a log file named VisualStudioD365Extension*.log is generated at a path similar to C:\Users\AppData\Roaming\Microsoft Corporation\Microsoft® Visual Studio®\16.11.32802.440\VisualStudioD365Extension-2022-08-12.log. +The correlation ID, client machine name, and timestamp are required for Microsoft to investigate. The correlation ID is in the Visual Studio output pane. +The logs are also written to Microsoft.PowerPlatformVSExtension*.log files in C:\Users\\AppData\Local\Microsoft\Dynamics365\Logs. +Additionally, a log file named VisualStudioD365Extension*.log is generated at a path similar to C:\Users\AppData\Roaming\Microsoft Corporation\Microsoft® Visual Studio®\\VisualStudioD365Extension-*.log. ### How do I monitor and diagnose deployed code running in the unified environment?