diff --git a/power-platform/developer/TOC.yml b/power-platform/developer/TOC.yml index 7b1543a55..4607e6cfb 100644 --- a/power-platform/developer/TOC.yml +++ b/power-platform/developer/TOC.yml @@ -35,7 +35,7 @@ href: appsource\appendix-add-license-information-to-your-solution.md - name: Use Power Platform CLI with the catalog (preview) href: submit-catalog-items.md - - name: Unified developer experience for finance and operations apps (preview) + - name: Unified developer experience for finance and operations apps items: - name: Overview href: unified-experience\finance-operations-dev-overview.md diff --git a/power-platform/developer/unified-experience/finance-operations-debug.md b/power-platform/developer/unified-experience/finance-operations-debug.md index 58b29b3f1..23617538c 100644 --- a/power-platform/developer/unified-experience/finance-operations-debug.md +++ b/power-platform/developer/unified-experience/finance-operations-debug.md @@ -9,9 +9,7 @@ ms.author: pvillads ms.subservice: developer --- -# Write, deploy, and debug X++ code (preview) - -[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] +# Write, deploy, and debug X++ code The unified developer experience for finance and operation apps enables you to write code on your local development computer and run it inside a cloud service. There exists a separation of functionality between these two tiers (local and cloud). @@ -26,7 +24,17 @@ This article shows you how to: Let's begin by developing a runnable X++ class to use as an example. The class's only task is to log a message into the Infolog. The important thing here isn't what the runnable class does, rather it's how we compile, run, and debug it. If you want to learn about the X++ language, see the [programming reference](/dynamics365/fin-ops-core/dev-itpro/dev-ref/xpp-language-reference). -As a prerequisite, you need to have completed setting up your local Visual Studio developer environment. More information: [Install and configure development tools (preview)](finance-operations-install-config-tools.md) + +> [!IMPORTANT] +> You can learn more by watching presentation and demos done for the Dynamics 365 FastTrack Tech Talk series +> +>[Unified Development Experience for Finance and Operations | Dynamics 365 FastTrack Tech Talk](https://www.youtube.com/watch?v=OuEZ1rXkpYY) + + +## Prerequisites + +You should have access to a unified developer environment, the Visual Studio tools extensions installed and configured on your developer machine and connected to the same environment. It's important to keep the metadata changes on your developer machine deployed to the connected environment . +More information: [Install and configure development tools](finance-operations-install-config-tools.md) ## Create a model @@ -92,7 +100,7 @@ At this point you're accessing the endpoint in the cloud, so unless you are alre > > 5. Synchronize the database for all models without deploying anything new via **Dynamics 365** > **Synchronize database...**. -You can follow the progress of the deployment by navigating to the "FinOps Cloud Run-time" channel in the Visual Studio output window. Once that deployment is complete, you can see log information by following the link displayed in the output window. +You can follow the progress of the deployment by navigating to the "FinOps Cloud Runtime" drop down in the Visual Studio output window. Once that deployment is complete, you can see log information by following the link displayed in the output window. ## Debug the deployed code @@ -116,7 +124,7 @@ Let's now try that. Instead of tediously writing our own form all over again, us `https://?prt=initial&debug=vs&activityid=\&cmp=DAT&mi=SysUserSetup` -You'll now see the form that allows you to set the colors in Dynamic's open. +You'll now see the form that allows you to choose the colors. Now let's set a breakpoint in the form. @@ -125,7 +133,8 @@ Now let's set a breakpoint in the form. 1. Select the form, and select **View code** to open the editor with the source code for this form. 1. In that form, set a breakpoint in the `selectionChange` method in the ThemeChooser control. This code is triggered when the user selects a new color theme. 1. In the browser window, select one of the colored squares, let's say the red one. You'll hit the breakpoint. -1. Continue the execution by pressing F5. Another colored square is hit and the breakpoint is triggered again. +1. Continue the execution by pressing F10 or F5. Another colored square is hit and the breakpoint is triggered again. +1. You can watch the locals, set new breakpoints and do various debugging tasks. > [!IMPORTANT] > If you want to attach the debugger to the running AOS process in the unified environment use **Dynamics 365** > **Launch debugger**. @@ -138,10 +147,11 @@ Now let's set a breakpoint in the form. As a recap, here's a summary and the points to take away from this exercise. -We started with using Visual Studio to create a simple runnable class. After the compilation, the package needed to be pushed to the cloud endpoint for execution. X++ code can only be executed in the cloud, so we performed a deployment operation. Once the deployment was complete, we executed the code by setting a breakpoint and running the debugger. We then started a form from the browser, and noticed that breakpoints were hit correctly as the form was used, and we did'nt have to restart the debugger for that to happen. In fact, the debugger can be started by using the **Launch debugger** option on the **Extension** menu. You can then enter a URL in the browser and the breakpoints are hit. +We started with using Visual Studio to create a simple runnable class. After the compilation, the package needed to be pushed to the cloud endpoint for execution. X++ code can only be executed in the cloud, so we performed a deployment operation. Once the deployment was complete, we executed the code by setting a breakpoint and running the debugger. We then started a form from the browser, and noticed that breakpoints were hit correctly as the form was used, and we did not have to restart the debugger for that to happen. In fact, the debugger can be started by using the **Launch debugger** option on the **Extension** menu. You can then enter a URL in the browser, execute the scenario to debug and the breakpoints will be hit. ### See also +[Unified Development Experience for Finance and Operations | Dynamics 365 FastTrack Tech Talk](https://www.youtube.com/watch?v=OuEZ1rXkpYY) [Unit testing in the unified developer experience](finance-operations-testing.md) [Create and manage environments in the Power Platform admin center](/power-platform/admin/create-environment) [Manage Dynamics 365 apps](../../admin/manage-apps.md) diff --git a/power-platform/developer/unified-experience/finance-operations-dev-overview.md b/power-platform/developer/unified-experience/finance-operations-dev-overview.md index d7e499950..8d0c18623 100644 --- a/power-platform/developer/unified-experience/finance-operations-dev-overview.md +++ b/power-platform/developer/unified-experience/finance-operations-dev-overview.md @@ -1,5 +1,5 @@ --- -title: "Unified developer experience for finance and operations apps (preview)" +title: "Unified developer experience for finance and operations apps" description: Learn about developing code for finance and operations apps using the new Power Platform unified developer experience. author: pvillads ms.date: 08/22/2023 @@ -9,26 +9,19 @@ ms.author: pvillads ms.subservice: developer --- -# Unified developer experience for finance and operations apps (preview) - -[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] +# Unified developer experience for finance and operations apps The unified developer experience consolidates the disparate developer tools and environments across finance and operations apps and Power Platform to reduce friction and simplify working across these apps. Finance and operations apps provide a rich ecosystem for professional developers by using a metadata and code-based development environment for mission critical scenarios. Power Platform brings the ability to author solutions quickly and seamlessly using low-code development paradigms and leverages Microsoft Dataverse as the relational data store. Power Platform also adds the ability to build and deploy your solutions using a continuous integration and deployment (CI/CD) pipeline. -> [!IMPORTANT] -> - This is a preview feature. -> - Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback. - - ## Typical scenario Consider a typical scenario where a developer would create a simple app for capturing orders in Microsoft Power Apps and persisting the gathered data in Dataverse. By means of the data synchronization engines mentioned below, the data would be available for finance and operations apps to do the heavy lifting of determining whether the requested items are available and pricing, etc. The results would be available near real-time in Power Apps. ## Finance and operations app development -Development for finance and operations apps is accomplished in Visual Studio using the Visual Studio add-in. This development environment provides everything a professional developer would expect. The unified environment runs in the cloud, and because of that we have made several changes and improvements to the way a developer works with finance and operations apps. However, existing finance and operations app developers will find that the large majority of their workflows will not be different from what they are used to. The article [Write, deploy, and debug X++ code (preview)](finance-operations-debug.md) walks you through how to build X++ code, deploy it to the cloud, execute and debug it there. All other content that you are likely to find about finance and operations app development, like how to extend existing code, is likely to still hold true. +Development for finance and operations apps is accomplished in Visual Studio using the Visual Studio extension. This development environment provides everything a professional developer would expect. The unified environment runs in the cloud, and because of that we have made several changes and improvements to the way a developer works with finance and operations apps. However, existing finance and operations app developers will find that the large majority of their workflows will not be different from what they are used to. The article [Write, deploy, and debug X++ code](finance-operations-debug.md) walks you through how to build X++ code, deploy it to the cloud, execute and debug it there. All other content that you are likely to find about finance and operations app development, like how to extend existing code, is likely to still hold true. -More information: [Install and configure development tools (preview)](finance-operations-install-config-tools.md) +More information: [Install and configure development tools](finance-operations-install-config-tools.md) ## Power Platform @@ -57,11 +50,11 @@ Set up Visual Studio on your local development computer. ### See also -[Install and configure development tools (preview)](finance-operations-install-config-tools.md) -[Write, deploy, and debug X++ code (preview)](finance-operations-debug.md) -[Frequently asked questions (preview)](finance-operations-faq.md) -[Tutorial: Provision a new environment with an ERP-based template (preview)](../../admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md#tutorial-provision-a-new-environment-with-an-erp-based-template-preview) +[Install and configure development tools](finance-operations-install-config-tools.md) +[Write, deploy, and debug X++ code](finance-operations-debug.md) +[Frequently asked questions](finance-operations-faq.md) +[Tutorial: Provision a new environment with an ERP-based template](../../admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md#tutorial-provision-a-new-environment-with-an-erp-based-template-preview) [Develop and customize home page](/dynamics365/fin-ops-core/dev-itpro/dev-tools/developer-home-page) (Dynamics 365 legacy information) -[Unified admin experience for finance and operations apps (preview)](../../admin/unified-experience/finance-operations-apps-overview.md) +[Unified admin experience for finance and operations apps](../../admin/unified-experience/finance-operations-apps-overview.md) [!INCLUDE [footer-banner](../../includes/footer-banner.md)] diff --git a/power-platform/developer/unified-experience/finance-operations-faq.md b/power-platform/developer/unified-experience/finance-operations-faq.md index 71f576bc8..790e50452 100644 --- a/power-platform/developer/unified-experience/finance-operations-faq.md +++ b/power-platform/developer/unified-experience/finance-operations-faq.md @@ -1,5 +1,5 @@ --- -title: "Frequently asked questions (preview)" +title: "Frequently asked questions" description: FAQs for the Power Platform unified developer experience. author: pvillads ms.date: 05/22/2024 @@ -9,9 +9,7 @@ ms.author: pvillads ms.subservice: developer --- -# Frequently asked questions (preview) - -[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] +# Frequently asked questions This FAQ answers common questions regarding the unified developer experience for finance and operations apps. @@ -39,29 +37,28 @@ We currently don't have the capability to provision or update the environment to ## Developer setup (metadata download, configuration, connecting to an environment) -### I can't access SQL Server using my SQL Server Management Studio client running in a OneBox environment - -We don't currently have a solution for secure connection to SQL Server running behind a cloud endpoint. A TDS endpoint (like the one Dataverse has) is planned to provide read-only queries to a database from SQL Server Management Studio. There's also a JIT access that will allow you to access the data after providing authentication. - ### I connected to the environment from Visual Studio but didn't get any pop-up to download metadata -Ensure that the unified development environment you created is of type **Sandbox**. A **Trial** environment won't work. +Ensure that the unified development environment you created is a unified development environment of type **Sandbox**. A **Trial** environment won't work. ### The Configure Metadata option doesn't appear on the menu -When this option is missing from the menu, open the Infolog from the menu and retry. +When this option is missing from the menu, open the Infolog from the menu and retry. This is addressed in application version 10.0.39 and above. -### How do I download again the client assets +### How do I re download the client assets -When you connect to the unified development environment, the tool does a few checks and doesn't initiate download if the required assets were previously downloaded. In case you need to download again, simply rename/delete the child folder with the application version of the environment under %LOCALAPPDATA%\Microsoft\Dynamics365. +In Visual Studio from the **Tools** menu, select **Download Dynamics 365 FinOps assets**. ### PackagesLocalDirectory extraction doesn't complete -Use [7-Zip](https://www.7-zip.org/download.html) to extract the metadata. +You can configure settings using the Visual Studio setting **Tools** > **Options** > **Power Platform Tools**. +The option **Auto setup for Dynamics 365...** is enabled by default. This ensures you do not have to manually extract system metadata or create the metadata configuration. The tool will do this for you. The Visual Studio output pane will inform you of any user action needed. + +If you still need to, try and use [7-Zip](https://www.7-zip.org/download.html) to extract the metadata. ### 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 @@ -75,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. @@ -95,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? @@ -111,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? @@ -131,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: @@ -140,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 @@ -151,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? @@ -161,4 +161,4 @@ Learn more about observability: [Monitoring and telemetry using Application Insi ### See also -[Unified developer experience for finance and operations apps (preview)](finance-operations-dev-overview.md) +[Unified developer experience for finance and operations apps](finance-operations-dev-overview.md) diff --git a/power-platform/developer/unified-experience/finance-operations-install-config-tools.md b/power-platform/developer/unified-experience/finance-operations-install-config-tools.md index b19261908..78d1277b0 100644 --- a/power-platform/developer/unified-experience/finance-operations-install-config-tools.md +++ b/power-platform/developer/unified-experience/finance-operations-install-config-tools.md @@ -11,20 +11,25 @@ contributors: - Pankaj-Thakur --- -# Install and configure development tools (preview) - -[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] +# Install and configure development tools This article describes how to install and configure required Visual Studio finance and operations tools into your local development environment. The instructions in each section should be followed in the order presented in this article. + > [!IMPORTANT] -> As a prerequisite, you need access to a [provisioned developer-focused sandbox environment](../../admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md). -> -> The user account you'll be using for development in the sandbox environment must be assigned the System Administrator role. -> The development machine should have at least 16 GB of free space on the local system drive to download the extension and metadata. -> The development machine running Microsoft Windows 10 or 11 must have Visual Studio 2022 installed with at least the .NET desktop development workload and the Modeling SDK. -> This SDK can be selected under individual components in the Visual Studio installer. Refer to [required Visual Studio components](/dynamics365/fin-ops-core/dev-itpro/dev-tools/developer-tools-vs2017#required-visual-studio-components). -> Microsoft SQL Server Express LocalDB is installed by default with Visual Studio 2022, but you should [validate that you can connect to it with windows authentication](/sql/database-engine/configure-windows/sql-server-express-localdb?view=sql-server-ver16#start-localdb-and-connect-to-localdb). +> You can learn more by watching presentation and demos done for the Dynamics 365 FastTrack Tech Talk series +> +>[Unified Development Experience for Finance and Operations | Dynamics 365 FastTrack Tech Talk](https://www.youtube.com/watch?v=OuEZ1rXkpYY) + + +## Prerequisites + +- As a prerequisite, you need access to a [provisioned developer-focused sandbox environment](../../admin/unified-experience/tutorial-deploy-new-environment-with-ERP-template.md). +- The user account you'll be using for development in the sandbox environment must be assigned the System Administrator role. +- The development machine should have at least 16 GB of free space on the local system drive to download the extension and metadata. +- The development machine running Microsoft Windows 10 or 11 must have Visual Studio 2022 installed with at least the .NET desktop development workload, the Modeling SDK and few other components. +- This SDK and other components can be selected and installed from the individual components pane in the Visual Studio installer. Refer to [required Visual Studio components](/dynamics365/fin-ops-core/dev-itpro/dev-tools/developer-tools-vs2017#required-visual-studio-components). +- Microsoft SQL Server Express LocalDB is installed by default with Visual Studio 2022, and you should [validate that you can connect to it with windows authentication](/sql/database-engine/configure-windows/sql-server-express-localdb#start-localdb-and-connect-to-localdb). ## Install the Power Platform extension for Visual Studio @@ -65,7 +70,7 @@ After installing the Power Platform Tools extension for Visual Studio, follow th ## Download and install the finance and operations extension and metadata -After installing the Power Platform Tools extension and connecting to the online Dataverse sandbox environment, you'll be presented with a dialog to download the finance and operations Visual Studio extension and metadata. +After installing the Power Platform Tools extension and connecting to the unified developer environment, you'll be presented with a dialog to download the finance and operations Visual Studio extension and metadata. :::image type="content" source="../media/devexp-fno-download.png" alt-text="Extension and metadata download dialog."::: @@ -108,10 +113,8 @@ Unpack the `PackagesLocalDirectory.zip` file as `PackagesLocalDirectory`. We rec > [!NOTE] > This is only required when the Visual Studio output pane indicates it is. -Using Windows File Explorer, from the folder specified below, open the `Microsoft.Dynamics.FinOps.ToolsVS2022.vsix` file to install the extension. -On first start of Visual Studio after updating/installing the Microsoft.Dynamics.FinOps.ToolsVS2022 VS extension, you will be prompted for elevated permissions for the extension to setup build targets, URLProtocoloHandler, etc. - -`C:\Users\\AppData\Local\Microsoft\Dynamics365\` +Using Windows File Explorer, from the folder `C:\Users\\AppData\Local\Microsoft\Dynamics365\`, open the `Microsoft.Dynamics.FinOps.ToolsVS2022.vsix` file to install the extension. +On first start of Visual Studio after updating/installing the Microsoft.Dynamics.FinOps.ToolsVS2022 VS extension, you will be prompted for elevated permissions for the extension to register the URLProtocoloHandler, setup build targets, to extract compiler files, etc. ### Configure the finance and operations extension @@ -145,8 +148,8 @@ To configure the extension, follow these instructions. |Cross reference database server| Set to `(localdb)\.` if you're using LocalDB, or `localhost` if you're using Microsoft SQL Server.| |Cross reference database name| The name for the cross reference database. The Visual Studio extension creates one if it doesn't exist.| |Application version to restore cross reference database from| Select this. It's populated from the assets downloaded when you connected to the unified developer environment.| -|Folder for your own custom metadata| Folder where your own code is (or will be).| -|Folders for reference metadata| Should contain at least the path where you have the extracted the PackagesLocalDirectory folder mentioned in [Extract system metadata](#extract-system-metadata).| +|Folder for your own custom metadata| Folder where your own X++ modules are (or will be).| +|Folders for reference metadata| Should contain at least the path where you have the extracted the PackagesLocalDirectory folder mentioned in [Extract system metadata](#extract-system-metadata). Also where you would add folders containing other reference modules; for example those received from ISVs.| #### Troubleshooting configuration @@ -164,9 +167,9 @@ More information: [SQL Server Express LocalDB](/sql/database-engine/configure-wi > [!NOTE] > If the cross reference database does not already exist, the tool will restore the database from the backup downloaded to C:\Users\\``\AppData\Local\Microsoft\Dynamics365\\``. You'll see notifications in the Visual Studio **Output** pane. If you need to restore it again by yourself you can do so after downloading with auto setup disabled. For instructions to do a database restore refer to [Restore to SQL Server](/sql/samples/adventureworks-install-configure?tabs=ssms#restore-to-sql-server). -#### Completeing configuration +#### Completing configuration -After the configuration is saved, you might get a prompt for elevation as administrator to register the protocol handler and to extract compiler files. Go ahead and accept these prompts. +After the configuration is created after a fresh installation of the extension, you might get a prompt for elevation as administrator to register the protocol handler and to extract compiler files. Go ahead and accept these prompts. Once the configuration completes, navigate to **View** > **Application Explorer** . You should see the **Application Explorer** window open. You might have to restart Visual Studio first. @@ -187,6 +190,6 @@ Start writing code, deploy, and debug. ### See also -[Unified developer experience for finance and operations apps (preview)](finance-operations-dev-overview.md) +[Unified developer experience for finance and operations apps](finance-operations-dev-overview.md) [!INCLUDE [footer-banner](../../includes/footer-banner.md)] diff --git a/power-platform/developer/unified-experience/finance-operations-pipeline-test.md b/power-platform/developer/unified-experience/finance-operations-pipeline-test.md index 07942f112..a5702425a 100644 --- a/power-platform/developer/unified-experience/finance-operations-pipeline-test.md +++ b/power-platform/developer/unified-experience/finance-operations-pipeline-test.md @@ -1,5 +1,5 @@ --- -title: "Execute unit tests in Azure Pipelines (Preview) " +title: "Execute unit tests in Azure Pipelines" description: Learn how to set up a unit test for execution using Azure Pipelines. author: pvillads ms.date: 05/10/2024 @@ -9,18 +9,13 @@ ms.author: pvillads ms.subservice: developer --- -# Execute unit tests in Azure Pipelines (preview) +# Execute unit tests in Azure Pipelines [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] An Azure Pipeline build task is available that lets users execute unit tests on connected cloud runtime environments using a continuous integration/continuous delivery (CI/CD) pipeline. The "Execute Unit Tests in Unified Environment" task is included in the [Dynamics 365 Finance and Operations Tools](https://marketplace.visualstudio.com/items?itemName=Dyn365FinOps.dynamics365-finops-tools) extension. -More information: [Continuous integration and deployment (preview)](finance-operations-pipelines.md), [Build automation that uses Microsoft-hosted agents and Azure Pipelines](/dynamics365/fin-ops-core/dev-itpro/dev-tools/hosted-build-automation) - -> [!IMPORTANT] -> -> - This is a preview feature. -> - Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback. +More information: [Continuous integration and deployment](finance-operations-pipelines.md), [Build automation that uses Microsoft-hosted agents and Azure Pipelines](/dynamics365/fin-ops-core/dev-itpro/dev-tools/hosted-build-automation) ## Prerequisites @@ -93,8 +88,8 @@ The following screenshot shows the same reference name used in a unit test task: ### See also -[Unit testing (preview)](finance-operations-testing.md) -[Continuous integration and deployment (preview)](finance-operations-pipelines.md) +[Unit testing](finance-operations-testing.md) +[Continuous integration and deployment](finance-operations-pipelines.md) [Build automation that uses Microsoft-hosted agents and Azure Pipelines](/dynamics365/fin-ops-core/dev-itpro/dev-tools/hosted-build-automation) [Unit Test Framework](/dynamicsax-2012/developer/unit-test-framework) diff --git a/power-platform/developer/unified-experience/finance-operations-pipelines.md b/power-platform/developer/unified-experience/finance-operations-pipelines.md index de15122b0..012f9bf71 100644 --- a/power-platform/developer/unified-experience/finance-operations-pipelines.md +++ b/power-platform/developer/unified-experience/finance-operations-pipelines.md @@ -1,5 +1,5 @@ --- -title: "Continuous integration and deployment (preview)" +title: "Continuous integration and deployment" description: Learn how to set up continuous integration and deployment using Azure Pipelines. author: pvillads ms.date: 08/31/2023 @@ -9,7 +9,7 @@ ms.author: pvillads ms.subservice: developer --- -# Continuous integration and deployment (preview) +# Continuous integration and deployment [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] @@ -22,7 +22,7 @@ This article explains how to implement continuous integration and deployment (CI ## Install or update the latest build tools 1. Sign into the Power Platform admin center and select the environment you want to work in. In the **Organization Settings > Extensions** menu, locate and install the “Dynamics 365 Finance and Operations Tools” shared extension. -1. Add a **Create Deployable Package** task in your build pipeline, and ensure it contains task version 1. Ensure **Add Licenses to Deployable Package** has task version 1. If you have tasks with same name, then select "View Yaml" for the task to ensure it’s a preview task. +1. Add a **Create Deployable Package** task in your build pipeline, and ensure it contains task version 1. Ensure **Add Licenses to Deployable Package** has task version 1. 1. Locate and install the Power Platform Build Tools extension from **Organization Settings > Extensions > Browse Marketplace**. 1. Download the X++ NuGet packages with the required version and add them to your artifact feed. For details on this step refer to [Build automation that uses Microsoft-hosted agents and Azure Pipelines - Finance & Operations](/dynamics365/fin-ops-core/dev-itpro/dev-tools/hosted-build-automation). diff --git a/power-platform/developer/unified-experience/finance-operations-product-db-access.md b/power-platform/developer/unified-experience/finance-operations-product-db-access.md index 1ac398cf2..7e77a5c3b 100644 --- a/power-platform/developer/unified-experience/finance-operations-product-db-access.md +++ b/power-platform/developer/unified-experience/finance-operations-product-db-access.md @@ -9,12 +9,10 @@ ms.author: pathaku ms.subservice: developer --- -# Request credentials to access D365 finance and operations product database (preview) - -[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] +# Request credentials to access D365 finance and operations product database A developer at times benefits from read/write access to the product database. We enable you to request credentials just in time, right from within Visual Studio. -As explained in [Write, deploy, and debug X++ code (preview)](finance-operations-debug.md), the business data is hosted in the cloud. +As explained in [Write, deploy, and debug X++ code](finance-operations-debug.md), the business data is hosted in the cloud. This feature applies only to unified development environments. The developer needs to have the system administrator (sysAdmin) in the environment. To request credentials for database access, follow these steps: @@ -37,9 +35,16 @@ To request credentials for database access, follow these steps: 1. Multiple users can have an active credential each, in a given environment. 1. A user can have a credential each in multiple environments. + +> [!IMPORTANT] +> You can learn more by watching presentation and demos done for the Dynamics 365 FastTrack Tech Talk series +> +>[Unified Development Experience for Finance and Operations | Dynamics 365 FastTrack Tech Talk](https://www.youtube.com/watch?v=OuEZ1rXkpYY) + + ### See also -[Write, deploy, and debug X++ code (preview)](finance-operations-debug.md) +[Write, deploy, and debug X++ code](finance-operations-debug.md) [Unit testing in the unified developer experience](finance-operations-testing.md) [Create and manage environments in the Power Platform admin center](/power-platform/admin/create-environment) [Manage Dynamics 365 apps](../../admin/manage-apps.md) diff --git a/power-platform/developer/unified-experience/finance-operations-testing.md b/power-platform/developer/unified-experience/finance-operations-testing.md index f233eac45..1a2b8377d 100644 --- a/power-platform/developer/unified-experience/finance-operations-testing.md +++ b/power-platform/developer/unified-experience/finance-operations-testing.md @@ -1,5 +1,5 @@ --- -title: "Unit testing (preview)" +title: "Unit testing" description: Shows you how to create and run test cases. author: pvillads ms.date: 08/28/2023 @@ -9,9 +9,7 @@ ms.reviewer: pehecke ms.author: pvillads --- -# Unit testing (preview) - -[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] +# Unit testing This how-to article shows you how to create and run reliable test cases. @@ -19,7 +17,7 @@ This how-to article shows you how to create and run reliable test cases. You need to have a Power Platform unified developer experience installed and configured on your local machine and a Power Platform developer-focused sandbox environment linked to it. It's important to keep the cloud and local representation of the code the same (synchronized). -More information: [Install and configure development tools (preview)](finance-operations-install-config-tools.md) +More information: [Install and configure development tools](finance-operations-install-config-tools.md) ## Key concepts @@ -143,6 +141,6 @@ Creating a test specific module helps to keep test code together and manageable. ### See also -[Write, deploy, and debug X++ code (preview)](finance-operations-debug.md) +[Write, deploy, and debug X++ code](finance-operations-debug.md) [!INCLUDE [footer-banner](../../includes/footer-banner.md)] diff --git a/power-platform/developer/unified-experience/finance-operations-trace-parser.md b/power-platform/developer/unified-experience/finance-operations-trace-parser.md index 81d05f16d..178561f0f 100644 --- a/power-platform/developer/unified-experience/finance-operations-trace-parser.md +++ b/power-platform/developer/unified-experience/finance-operations-trace-parser.md @@ -11,15 +11,8 @@ ms.author: pvillads # Diagnose issues and analyze performance using the Trace Parser -[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] - This article explains how you can use the Trace Parser tool to consume traces and analyze performance in your unified developer experience deployment. The tool can visualize the execution of X++ methods and show execution call trees including the time spent in each method and the time spent for each database operation. -> [!IMPORTANT] -> -> - This is a preview feature. -> - Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback. - ## Finding the Trace Parser The Trace Parser tool is a desktop application running on the development (client) machine. When you download the metadata, cross reference database, or more for a particular application version, an installation program for the Trace Parser (named TraceParser.msi) is also downloaded. Use this MSI file to install the Trace Parser tool. When the tool is started the first time, it asks for a name for the database that holds the traces. Provide a name that allows you to distinguish the trace database from other databases on your server (for example "Traces").