New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Series Index

Microsoft Dynamics 365 Business CentralThis post is part of a series on the new functionality available in Wave 1 of Microsoft Dynamics 365 Business Central 2024. There are two release waves for Business Central each year, with functionality being released over the six months of the wave.

In this series of posts, I am going to take a look at what is new with Business Central in this release wave. My understanding is the announced new functionality will become available in the six months of the wave, so not all of it will be available immediately. When posting about some new functionality, I’ll try to indicate where something will be available in October or later. Microsoft do reserve the right to withdraw announced functionality before release; when this happens, I’ll try to publish an article on the removed functionality and update the original article I published.

This series index, below (assuming you’re reading this on azurecurve | Ramblings of an IT Professional), will automatically update as each post in the series goes live, so make sure you bookmark this post so you can see keep up-to-date with this series.

Continue reading “New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Series Index”

New Functionality In Microsoft Power Automate 2024 Wave 1: Ingest Process Data from Customers’ Data Lake

Power AutomateThis post is part of the New Functionality In Microsoft Power Automate 2024 Wave 1 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2024 Wave 1.

The 1st of the new functionality in the Process Mining section is ingest process data from customers’ data lake.

You no longer have to transform or port your data in specific sources for Process Mining. Instead, Power Automate Process Mining can connect directly to your existing data pipelines in your Azure data lake.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
Early Access: –
General Availability: Apr 2024

Feature Details

You now have a choice to enable Power Automate Process Mining to connect directly to your Azure data lake with your existing data pipelines. This eliminates steps of data transformation or porting across sources, enabling easier data ingestion. Direct connection to your Azure data lake also enables scaling process data to hundreds of gigabytes.

Click to show/hide the New Functionality In Microsoft Power Automate 2024 Wave 1 Series Index

New Functionality In Microsoft Power Automate 2024 Wave 1
Receive Intelligent License Recommendations for Admins
Be More Productive with Power Automate and Excel Desktop
View a Power Automate Visual in a Power BI Report
Monitor Performance for Cloud and Desktop Flow Activities
Connect to Other Environments from the Microsoft Dataverse Connector
Push Cloud Flow Execution Data into Application Insights
Use Your Own Encryption Key for Encrypting Data At-Rest for Existing Environments
Create Power Automate Flows in Excel
View Two Action Properties Panes Simultaneously
Use Undo and Redo While You Build Cloud Flows in the Designer
Use Copy-Paste for Container Actions Like Scope, Condition, and Apply to Each
Use a Simplified OData Editor in Actions like Get Items and Get Files
Manage Unpublished Solution-Aware Cloud Flows Using Admin APIs
Cancel all Flow Runs for a Version of a Flow
Create a Flow on a File in Teams
Cloud Flows are Automatically Defined in Dataverse Solutions
Get Quick Insights and Recommendations in Copilot for Process Mining
Generate Flow Description Using AI
Set Up Fallback UI Automation Mechanism
Power Fx Integration with Power Automate for Desktop
Use Power Platform Connectors in Power Automate for Desktop Actions
Use CyberArk Credentials in Desktop Flow Connections
Use Azure Key Vault Credentials in Flow Connections
Connect Your Own Virtual Network with Hosted Machine Group
View Attended Desktop Flow Runs Using Picture-in-Picture Execution Mode
Ingest Process Data from Customers' Data Lake

Working with Power Automate: What Are Environment Variables and Why Should They be Used?

Power AutomateThis article is part of the Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.

As I’ve commented in other articles, solutions should be used when developing Power Automate flows, and in fact form part of the recommended application lifecycle management (ALM) scenario of moving a flow between Power Automate environments.

Environment variables are only available within a solution and are used to store parameter keys and values used within the flows of the solution. This separation of settings from functionality allows the behaviour of a flow to be changed without needing to amend the flow in the development environment and the solution redeployed to the production environment.

While you can and should use environment variables for all parameters used by flows within a solution, the two which I would say should always be created for a flow used with Business Central are the ones for the environment and company.

The main benefits of using environment variables are:

  • Provide new parameter values while importing solutions to other environments.
  • Store configuration for the data sources used in canvas apps and flows. For example, SharePoint Online site and list parameters can be stored as environment variables; therefore allowing you to connect to different sites and lists in different environments without needing to modify the apps and flows.
  • Package and transport your customization and configuration together and manage them in a single location.
  • Package and transport secrets, such as credentials used by different components, separately from the components that use them.
  • One environment variable can be used across many different solution components – whether they’re the same type of component or different. For example, a canvas app and a flow can use the same environment variable. When the value of the environment variable needs to change, you only need to change one value.
  • Additionally, if you need to retire a data source in production environments, you can simply update the environment variable values with information for the new data source. The apps and flows don’t require modification and will start using the new data source.
  • Supported by SolutionPackager and DevOps tools enable continuous integration and continuous delivery (CI/CD).
  • The environment variables can be unpacked and stored in source control. You may also store different environment variables values files for the separate configuration needed in different environments. Solution Packager can then accept the file corresponding to the environment the solution will be imported to.

More details on environment variables are available on < ahref='https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables'>Microsoft Learn.

Working with Power Automate

Working with Power Automate
What is Power Automate?
What Type of Flow Are Available?
What Type of Cloud Flows Are Available?
Power Automate with Business Central
Working with Power Automate Solutions: What Are Solutions?
Working with Power Automate Solutions: What Types of Solution Are There?
Working with Power Automate Solutions: What is a Solution Publisher?
Working with Power Automate Solutions: Create a Solution Publisher
Working with Power Automate Solutions: Create a Solution
Working with Power Automate Solutions: Publish a Solution
Working with Power Automate Solutions: Version Numbering for Solutions
Working with Power Automate Solutions: Exporting An Unmanaged Solution
Working with Power Automate Solutions: Importing An Unmanaged Solution
Working with Power Automate Solutions: Exporting A Managed Solution
Working with Power Automate Solutions: Importing A Managed Solution
Working with Power Automate Solutions: Change the Managed Properties of a Solution Component
Create a Visio Diagram of a Flow
What Are Environment Variables and Why Should They be Used?
Create an Environment Variable
Create a New Cloud Flow From a Template
Managing Large Flows
What is a Scope?
Example of How to Use a Scope
Best Practice For Using Scopes
Working with Power Automate Child Flows: What are Child Flows?
Working with Power Automate Child Flows: Create a Child Flow
Working with Power Automate Child Flows: Change Run Only Users For Child Flow
Working with Power Automate Child Flows: Add a Child Flow To a Parent Flow
Working with Power Automate Child Flows: Test the Parent/Child Flow Examples
Working with Power Automate Child Flows: Error Encountered Saving a Flow Which Calls a Child Flow
Working with Power Automate Child Flows: Error Encountered With Surprise Extra Parameters for a Child Flow