Azure OpenAI is a cloud-based service offered by Microsoft that provides access to advanced artificial intelligence models developed by OpenAI. It empowers developers to integrate these powerful models into their applications without requiring extensive expertise in AI development or infrastructure management.

Inogic aims to transform the way businesses function by developing advanced AI-driven applications with integrated AI Models provided by Azure OpenAI for Dynamics 365 and Power Platform. The Team offers to develop functional applications for businesses helping with interactive client conversations, virtual assistance, content generation and translation, report analysis, buying assistance, end-to-end management, and more!

What Inogic Offers?

Inogic Offers –

Consultation & Development of Applications

Team Inogic’s AI experts craft bespoke AI apps that integrate seamlessly with your business, boosting sales and efficiency. They unlock hidden potential and transform it into powerful engines driving conversions and optimizing workflows.

Configuration Setup to accommodate them

Our proactive team closely monitors and maintains your AI app, guaranteeing optimal performance and adapting to evolving business needs. We’re reliable partners throughout the app’s lifecycle, readily available for any questions or fine-tuning.

Reporting and Analysis Assistance

Inogic leverages Azure OpenAI’s power to create cutting-edge reporting applications. These applications utilize predictive analytics and intelligent visualizations to anticipate market shifts, automate reports, and extract valuable insights from complex data.

Decision-Making Setup

Team Inogic harnesses Azure OpenAI’s algorithms to build AI-powered decision engines. These applications analyze complex data, uncover hidden patterns, predict trends, and suggest optimal actions, paving the way for automated and data-driven strategic decisions.

Azure Open AI Application developed by Inogic – Buyer Behaviour Analysis

In the bustling world of business, understanding your customers is key to success. But deciphering their true feelings can be like trying to read tea leaves. That’s where Team Inogic stepped in, armed with a revolutionary solution: an AI-powered application that listens beyond words, analyzing sentiment for enhanced sales and deeper customer relationships.

Imagine a world where every customer interaction, from emails to chat messages, becomes a window into their emotions. This is the magic of Inogic’s application. Powered by the invisible hand of Power Automate, it seamlessly extracts comments from client conversations, feeding them into the Azure OpenAI Services. This powerhouse of AI then analyzes the sentiment hidden within, categorizing it as negative, positive, or neutral.

The results? A treasure trove of insights displayed right within your CRM and individual client accounts. Each interaction is visualized on a timeline, painting a clear picture of the customer’s emotional journey. This allows you to see not just the “what” of their communication, but the crucial “why.”

Armed with this newfound understanding, sales teams can now predict with greater accuracy whether a client is likely to convert and become a long-term partner. This empowers them to tailor their approach, addressing concerns, fostering positive interactions, and ultimately strengthening relationships.

But the benefits extend far beyond sales. By identifying negative sentiments early on, customer service teams can proactively address issues, preventing frustration and fostering loyalty. This proactive approach builds trust and strengthens the bond between your business and your customers.

Inogic’s sentiment analysis application is a testament to the power of AI in transforming customer relationships. It’s not just about technology; it’s about harnessing the power of listening to truly understand the hearts and minds of your customers. In a world where genuine connection is paramount, Inogic’s innovation paves the way for a future of deeper, more meaningful interactions, ultimately leading to sustained success.

What’s More?

Inogic Services division is also popular as a Power Apps Dedicated Offshore Developer, an expert in Dynamics 365 Development Services, Power Platform Technical Support and Consultation, and much more!

The Professional Services Division of Inogic designs and develops AI applications for clients using Copilot in Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Copilot Power Apps. The division also provides services to create AI-enabled conversational chatbots using Copilot Studio.

Check out our Website or write to the experts at crm@inogic.com

Be progressive with Inogic Professional Services!

The post Power Automate with Azure OpenAI Services to analyze Buyer Behaviour – an AI app by Inogic! first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post Power Automate with Azure OpenAI Services to analyze Buyer Behaviour – an AI app by Inogic! appeared first on Microsoft Dynamics 365 Blog.

Recently, we got a requirement to check whether a specific date is a business/working day considering weekends and public holidays defined in the Service calendar of CRM.

Below are the workdays defined in the CRM:

Below is the list of holidays defined in the CRM which are observed:

Given a specific date, we were supposed to check whether it is a working day considering the weekends and public holidays defined above.

The Power Automate Flow steps to get Working Days per week

Step 1: Retrieve Calendar (Customer Service Type)

First, add the ‘List Records’ step to retrieve the ‘Customer Service’ type Calendar. Use a filter query to fetch the calendar by its name and type. To capture the necessary GUID for the next step.

Step 2: Retrieve Calendar (Working Days)

Now, proceed to fetch the working days for the previously obtained calendar. Utilize an ‘Apply to Each’ step to iterate through each calendar, and within that, add a ‘Get a Row by ID’ action to retrieve the working day’s calendar using the expand query. The expanded query allows us to seamlessly expand related tables in the list rows action. In this case, the main table is Calendar while the related table is Calendar Rules where the weekly working days pattern is stored.

In the ‘Compose’ action, we can find the calendar working days enumerated. Using the following formula:

If (    empty(outputs('Get_a_Calendar_which_contains_working_days')?['body/calendar_calendar_rules'][0]?['pattern']), -1, Substring (      outputs('Get_a_Calendar_which_contains_working_days')?['body/calendar_calendar_rules'][0]?['pattern'],        add(indexOf(outputs('Get_a_Calendar_which_contains_working_days')?['body/calendar_calendar_rules'][0]?['pattern'], 'BYDAY='), length('BYDAY=')) ) )

The Power Automate Flow steps to get Holidays

Step 1: Retrieve Calendar (Holiday Schedule Type)

First, use the ‘List Records’ step to retrieve the ‘Holiday Schedule’ type Calendar. Apply a filter query to fetch the calendar by its name and type. The result will provide the necessary GUIDs for the next step.

Step 2: Retrieve Calendar Rules (Holidays)

Now, proceed to fetch the calendar rules for the previously obtained calendar. Utilize an ‘Apply to Each’ step to iterate through each calendar, and within that, add a ‘Get a Row by ID’ action to retrieve the calendar rule.

However, note that attempting to fetch the calendar rule directly will result in an error saying “The ‘Retrieve’ method does not support entities of type ‘calendarrule’”,

As a workaround, we can retrieve the calendar rules along with calendar data using the expand query.

In the ‘Compose’ action, we can find the calendar rules enumerated using the following formula:

outputs(‘Get_a_calendar_which_contains_holidays’)?[‘body/calendar_calendar_rules’]

Step 3: Get Holidays details

For each calendar rule, implement an ‘Apply to Each’ loop. Within this loop, incorporate a Compose action to extract the holiday name, as illustrated.

Conclusion

Using Power Automate, we can retrieve Calendar and Calendar Rule details which allows users to handle complex requirements, such as checking working days while considering weekends and defined holidays.

The post Get working days and holidays of the CRM Service calendar in Power Automate Flow first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post Get working days and holidays of the CRM Service calendar in Power Automate Flow appeared first on Microsoft Dynamics 365 Blog.

A custom action in desktop flow is a feature designed to automate repetitive tasks seamlessly.
This blog provides a comprehensive guide on designing and leveraging custom actions in the desktop version of Power Automate flows. The journey starts with a step-by-step procedure to create these custom actions, offering a detailed walkthrough of the process to upload them within the desktop Power Automate flows environment.

Certainly! In this scenario, a custom action in the desktop flow is employed to automatically download files linked to various activities. Whether these files are attachments or stored in notes, the custom action streamlines the process, offering users the flexibility to choose a personalized destination path for efficient file organization. This automation enhances efficiency, saves time, and empowers users with control over their file management preferences.

Pre-requisite: To create custom action in Power Automate for desktop flows you need the following things:

1. NET Framework 4.7.2 SDK or above.

2. Visual Studio 2022 or above

3. Power Automate desktop v2.32 or above.

4. The Action SDK

Step 1: Create a custom action

Open Visual Studio 2022 -> Create sample project -> Go to Tools -> Nugget Package Manager -> Package Manager Console.

Run the below commands inside the NuGet Package Console.

Action SDK:
NuGet\Install-Package Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK -Version 1.4.232.23122-rc

Power Automate desktop – Visual Studio templates:

dotnet new install Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.Templates::1.0.0-rci

Create a new power automate project as mentioned below.

Once a project is created successfully, you can proceed with the code. In this illustration we have written /used the below code however it may vary depending upon the use case or the actual scenario.

using System; using System.IO; using Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK; using Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.Attributes; namespace Modules.CustomActions {     [Action(Id = "Action1", Order = 1, FriendlyName = "Custom Action", Description = "The action is used to download notes/attachments")]     [Throws("ActionError")] // TODO: change error name (or delete if not needed)     public class Action1 : ActionBase     {         #region Properties         // File path where the downloaded file will be stored         [InputArgument(FriendlyName = "File Path", Description = "File Path")]         public string filepath { get; set; }           // File path where the downloaded file will be stored         [InputArgument(FriendlyName = "Document Body", Description = "document Body")]         public string documentBody { get; set; }         // The name of the file to be created         [InputArgument(FriendlyName = "File Name", Description = "File Name")]         public string fileName { get; set; }         #endregion         #region Methods Overrides         // Override of the Execute method in the base class         public override void Execute(ActionContext context)         {             try             {                 // Concatenate the file path and file name                 filepath = filepath + "\\" +fileName;                 // Create a file stream to write the file data                 using (FileStream data = File.Create(filepath))                 {                     // Convert Base64 document body to byte array                     byte[] fileBytes = Convert.FromBase64String(documentBody);                     // Write the byte array to the file stream                     data.Write(fileBytes, 0, fileBytes.Length);                 }             }             catch (Exception e)             {                 // Handle exceptions and throw an ActionException                 if (e is ActionException) throw;                 throw new ActionException("ActionError", e.Message, e.InnerException);             }         }         #endregion     } }

Build the project.

Step 2: Creating and importing a self-signed certificate

Open Windows PowerShell.

Copy and paste the following commands, replacing the underlined names as appropriate.

$certname = "CustomActionCertificate" $cert = New-SelfSignedCertificate -CertStoreLocation Cert:\CurrentUser\My -Type CodeSigningCert -Subject "CN=$certname" -KeyExportPolicy Exportable -KeySpec Signature -KeyLength 2048 -KeyAlgorithm RSA -HashAlgorithm SHA256 $mypwd = ConvertTo-SecureString -String "pass@word1" -Force -AsPlainText Export-PfxCertificate -Cert $cert -FilePath "D:\Task\Blog\CustomActionCertificate.pfx" -Password $mypwd

After generating and exporting the certificate, incorporate it into your trust root. Then, double-click on the exported certificate. Kindly complete all the steps in import vizard.

Click Next

Write down the password that was used in the certificate creation command.

In the certificate store, select ‘Trusted Root Certification Authorities.’ Then click on ‘Next,’ and after that, simply click on ‘Finish.’ You will receive a message indicating that the import was successful.

Step 3: – Sign the .dll file using a trusted certificate by running the following command in a Developer Command Prompt for Visual Studio, replacing names as appropriate.

Signtool sign /f “D:\Task\Blog\CustomActionCertificate.pfx” /p pass@word1 /fd SHA256 “D:\Task\Blog\Modules.CustomActions\Modules.CustomActions\bin\Debug\net472\Modules.CustomActions.dll”

Step 4: – Packaging everything in a cabinet file

The .dll containing the custom actions and all its dependencies (.dll files) must be packaged in a cabinet file (.cab).

Create a Windows PowerShell Script (.ps1) containing the following lines & save it as Script[makeCabFile.ps1].

param( [ValidateScript({Test-Path $_ -PathType Container})] [string] $sourceDir,         [ValidateScript({Test-Path $_ -PathType Container})] [string] $cabOutputDir, [string] $cabFilename ) $ddf = ".OPTION EXPLICIT .Set CabinetName1=$cabFilename .Set DiskDirectory1=$cabOutputDir .Set CompressionType=LZX .Set Cabinet=on .Set Compress=on .Set CabinetFileCountThreshold=0 .Set FolderFileCountThreshold=0 .Set FolderSizeThreshold=0 .Set MaxCabinetSize=0 .Set MaxDiskFileCount=0 .Set MaxDiskSize=0 " $ddfpath = ($env:TEMP + "\customModule.ddf") $sourceDirLength = $sourceDir.Length; $ddf += (Get-ChildItem $sourceDir -Filter "*.dll" | Where-Object { (!$_.PSIsContainer) -and ($_.Name -ne "Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.dll") } | Select-Object -ExpandProperty FullName | ForEach-Object { '"' + $_ + '" "' + ($_.Substring($sourceDirLength)) + '"' }) -join "`r`n" $ddf | Out-File -Encoding UTF8 $ddfpath makecab.exe /F $ddfpath Remove-Item $ddfpath

Step 5: – Use the following command to create a .cab file in PowerShell.

.\makeCabFile.ps1 “D:\Task\Blog\Modules.CustomActions\Modules.CustomActions\bin\Debug\net472” “D:\Task\Blog” CustomActions.cab

Step 6: – The .cab file must also be signed. Use the following command to sign the .cab file in a Developer Command Prompt for Visual Studio, replacing names as appropriate.

Signtool sign /f “D:\Task\Blog\CustomActionCertificate.pfx” /p pass@word1 /fd SHA256 “D:\Task\Blog\CustomActions.cab”

Step 7: Upload custom actions

Go to Power Automate -> More -> Discover all -> Data -> Custom Action.

Select ‘Upload custom action’ and upload the .cab file. However, note that we can upload .cab files up to 30MB.

Step 8: Use custom actions

You can include custom actions in the desktop flow through the ‘Assets library’ using Power Automate Desktop Designer.

To use the ‘Assets library,’ select it in the designer. Alternatively, use the Tools bar.

In the Assets library, we can see all the custom actions we have uploaded. We can add a custom action, and we can also remove previously added custom actions.

Now, we can use our custom action.

Double-click on the custom action to add it.

Here, documentBody and FileName are variables taking input from the cloud flow. Choose the file path where you want to store the downloaded attachment or notes.

We created an automated cloud flow that triggers when a file is added to notes. Then, we check if the document is present or not in a condition. If the document is present, we call a desktop flow, select the run mode, and pass documentBody and fileName.

Here, I am adding a docx file to the note.

Finally, the file is downloaded or stored in my selected path automatically

Conclusion

Thus, we learned how to utilize the custom actions with the Power Automate Desktop Flows

The post Custom Actions with Power Automate Desktop Flows first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post Custom Actions with Power Automate Desktop Flows appeared first on Microsoft Dynamics 365 Blog.

This year we experienced a surge in new ways to work day to day all thanks to new Advancements in AI. With various brands and tech giants put up their version of AI for public use cases, back in June Microsoft unveiled their take on AI enabled system, the infamous – Copilot, a collaborative tool designed to reduce digital debt and enhance productivity, freeing up people to focus on tasks that require a uniquely human touch.

With the new announcements at Microsoft Ignite 2023, the flagship event for IT Devs and Business Folks, everyone got to know about the new products, features and updates and way forward with Copilot and other AI enabled in Microsoft Ecosystem (Power Platform, Dynamic 365, Microsoft Suite, Azure, Dataverse, etc.)

Attendees also learned about the latest advancements in cloud computing, artificial intelligence, productivity, and collaboration. Moreover, they had the chance to network with other Microsoft professionals and get hands-on experience with the latest Microsoft products and services.

If you want to keep up with the latest news and updates from the event, check out the Microsoft Ignite 2023 Book of News

With all the new buzz that accompanies Copilot, comes a lot of questions like

Copilot’s impressive capabilities continue to grow with each update, and this speaks volumes about its potential. But enough with the fanboying – let’s dive into the exciting new Power Platform and other major announcements from Microsoft Ignite.

Microsoft Ignite 2023 has brought some exciting updates to the Power Platform. One of the most significant updates are for Power Apps.

Exciting Power Apps Updates Revealed at Microsoft Ignite 2023

The Power Apps has seen significant updates and improvements, particularly. One of the most noteworthy changes is the rendering of mobile apps natively on devices. This update enhances the user experience with smoother animations, better performance, and increased reliability. This truly native mobile UI/UX feature also offers the latest mobile interaction patterns to users. Additionally, users can now use apps offline, along with the recently introduced modern controls.

Another exciting feature focuses on Copilot, which is available to every user of Microsoft Dataverse-backed canvas apps. Now, Copilot allows users to ask questions about their data with a single click, without any action needed from makers. This Copilot feature is entering a limited preview in December 2023 and ends by March 2024. All Dataverse-backed canvas apps will now include this feature by default, but you’re still in charge. As a maker, you can turn off this functionality for your apps whenever you want.

Microsoft has announced a new feature for Dataverse-backed canvas apps with Copilot. With this feature, users can easily ask data-related questions to Copilot with a single click, without needing any assistance from app makers. This feature will be in limited preview mode starting in December 2023 and will end by March 2024. However, it will be automatically available to all Dataverse-backed canvas apps. Makers can rest assured, as they will maintain full control over the feature and can disable it at any time.

Microsoft Unveils Copilot Studio: An Innovative Low-Code Tool for Developers

Microsoft recently unveiled Copilot Studio at the Ignite event. This innovative low-code tool provides developers with the ability to customize Microsoft Copilot for Microsoft 365, as well as develop standalone copilots. Copilot Studio offers a range of powerful conversational capabilities, including GPT customization, generative AI plugins, and manual topics. This allows users to seamlessly personalize Copilot for Microsoft 365 with their own enterprise scenarios. With Copilot Studio, users can quickly build, test, and publish standalone copilots and custom GPTs.

Additionally, the tool provides essential features such as access management, data security, user controls, and analytics. The limited preview of the feature is expected to begin in December 2023, with the full preview available to all by the end of March 2024.

Microsoft Fabric: A Revolutionary End-to-End Analytics Product

Microsoft Fabric is an innovative analytics product that consolidates an organization’s data and analytics into a single platform. This inclusive software allows users to create generative AI experiences via services like Azure AI Studio and Copilot. Currently, the product is widely used, with 25,000 businesses worldwide implementing it.

Power BI and Microsoft Fabric Integration

Integrate Power BI with Microsoft Fabric to generate reports and summaries from the data within the Fabric platform. With Copilot, users can quickly generate insights and narratives in seconds. Additionally, data from Dynamics 365 or Power Platform can be linked to Fabric without the need to export data or build pipelines.

Copilot: The Revolutionary Feature of Microsoft Fabric

Copilot is a new feature in Microsoft Fabric that provides users with access to large language models such as GPT. With natural language or prompts, users can instruct Copilot to perform specific tasks. This feature is now in public preview and is available for Power BI, Data Factory, Data Engineering, and Data Science experiences.

Discover New Capabilities with Power Automate: Enhanced Process Mining, RPA, and Orchestration Features

Power Automate has recently introduced new features to its existing Copilot capabilities, offering users a range of new experiences. Copilot is now equipped to aid users with desktop flows (RPA) by answering their questions and providing step-by-step instructions and relevant information from documentation. Additionally, users can generate scripts by simply describing the task they wish to perform, and the Copilot feature will automatically generate the corresponding code.

Introducing Copilot: The Ultimate Solution for Analyzing Automation Activity

Orchestration is essential for building and operating automation at scale. Copilot’s new experience enables CoE teams to unlock new use cases for their monitoring and governance strategies. It democratizes access to insights, helping automation stakeholders to easily analyze the health and performance of their automation by using natural language queries.

Admins and business users with access to flow histories can query past runs across their environments, which helps in monitoring tasks and detecting potential issues in flows. Copilot is a game-changer for makers, small teams, or part of a Center of Excellence (CoE), as it provides the necessary insights for greater success. If you haven’t established a CoE yet, our automation kit can help you get started.

New Possibilities with Copilot’s Integration into Power Pages

Copilot has already been integrated into Power Pages, enabling creators to develop websites, web pages and forms with natural language. Now, creators can take it a step further and design websites that allow payments, opening up new opportunities for applications.

Microsoft Introduces Copilot as Bing Chat’s Rebranded and Expanded AI Chat Interface

Microsoft’s Bing Chat is now Copilot, universalizing the AI chat interface for Windows 11, Bing, and Edge. Moreover, Microsoft has added new AI features to Copilot, including Copilot for Azure, Copilot for Service, Copilot Studio, and Copilot in Dynamics 365 Guides.

Microsoft Unveils Two New Custom Chips for Cloud Infrastructure

Microsoft is continuing to push the boundaries of AI with the introduction of two new, custom-designed chips for its cloud infrastructure. The Azure Maia 100 is solely optimized for artificial intelligence (AI) tasks and generative AI, while the Azure Cobalt 100 is a CPU chip that uses the Arm Neoverse CSS design to enhance both performance and energy efficiency in general cloud services on Azure. These chips will be implemented in Azure data centers early in 2024, demonstrating Microsoft’s commitment to providing innovative AI solutions that cater to customer needs and enhance its supply chain.

Microsoft Introduces Loop, Its Rival to Notion

Microsoft has unveiled its latest collaboration hub, Microsoft Loop, which aims to rival Notion and other similar platforms. Loop is specifically engineered to sync across all Microsoft 365 apps and services, providing users with workspaces and pages to organize their tasks, projects, and documents. What sets Loop apart from its competitors is the seamless integration with the Microsoft 365 suite. Loop is now accessible to users in public preview mode.

Microsoft’s Copilot: Now Revolutionizing Security Management

Microsoft is leading the way in creating a unified security operations platform by combining its Sentinel and Defender XDR platforms. The addition of Security Copilot chatbot to this framework brings cutting-edge conversational AI capabilities to IT and security teams, resulting in simplified and streamlined security management. These advancements are a crucial step forward in improving security measures.

Conclusion

Microsoft’s Power Platform can be significantly enhanced with the use of Copilot – natural language and generative AI capabilities, Copilot can help you automate, analyze data, develop apps, and even create content. Copilot can increase your productivity, efficiency, and creativity, making it easier for you to reach your objectives.

If you haven’t tried Copilot yet, you’re missing out on an amazing opportunity to take your business to the next level. Inogic is here to help you develop Power Apps, Power Automate, Power BI, or Power Pages using Copilot. As your trusted advisor, we understand your unique business needs and can help you achieve your goals.

Visit Inogic’s website or contact us at crm@inogic.com to learn more about our Power Platform Professional Services and how you can leverage the power of Copilot.

The post Copilot and Power Platform: Highlights from Microsoft Ignite 2023 and What They Mean for You! first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post Copilot and Power Platform: Highlights from Microsoft Ignite 2023 and What They Mean for You! appeared first on Microsoft Dynamics 365 Blog.

The post Dynamics 365 – Send a Customer Case with Azure SMS appeared first on Ellipse Solutions.

Source

The post Dynamics 365 – Send a Customer Case with Azure SMS appeared first on Microsoft Dynamics 365 Blog.

The post Dynamics 365 Connected Customer Service Example appeared first on Ellipse Solutions.

Source

The post Dynamics 365 Connected Customer Service Example appeared first on Microsoft Dynamics 365 Blog.

Microsoft Fabric is an end-to-end data analytics solution in the cloud, and one of its workloads is called Data Factory. In this article, you will learn what Data Factory is, how it works with the rest of Microsoft Fabric, and what are elements and functions of Data Factory.

Video

Microsoft Fabric

To understand Data Factory, it is best to understand Microsoft Fabric first. Microsoft Fabric is an end-to-end Data Analytics software-as-a-service offering from Microsoft. Microsoft Fabric combined some products and services to cover an end-to-end and easy-to-use platform for data analytics. Here are the components (also called workloads) of Microsoft Fabric.

To learn more about Microsoft Fabric and enable it in your organization, I recommend reading the articles below;

• What is Microsoft Fabric
• How to enable Fabric in your organization

Data Factory Origin

Microsoft Fabric has a workload for Data Integration. Any end-to-end data analytics system should have a data integration component. Microsoft has been a strong data integration tool and service leader for decades. This started with SQL Server tools such as DTS (Data Transformation Service) and SSIS (SQL Server Integration Services) and then stepped into cloud-based technologies such as ADF (Azure Data Factory). Microsoft also used a data transformation engine that first targeted citizen data analysts called Power Query.

Data Factory is the data integration component of Microsoft Fabric which brings the power of Azure Data Factory and Power Query Dataflows into one place. For many years, we had these two technologies doing data transformations separately. But now, these two are combined under Fabric, called Data Factory.

Power Query

Power Query Dataflows was first announced a few years ago as an additional component to Power BI for data transformation as a cloud technology that is simple to use for data analysts. But soon, it became more than just for Power BI; it became Power Platform Dataflows. These days, Power Query Dataflows are used for data transformations in Power BI projects and data migration in Power Apps projects.

Although Power Query Dataflows is also on the dataflow side, it needed some enhancements on scalability and the control of execution with some control flow elements (such as loop structures, conditional execution, etc.).

Azure Data Factory

Azure Data Factory came into the market many years ago as the next generation of SSIS for in-the-cloud ETL. However, the data transformation engine of Azure Data Factory was not built on a strong basis, so most of the time, ADF was used for data ingestion, and then with the help of SQL stored procedures, etc., for doing the transformation afterward. ADF was not a tool for citizen data analysts. It was instead for data engineers and developers. ADF used data pipelines to execute a group of activities as a flow, and among those activities, there were tasks such as copy data, running a stored procedure, etc.

For the past few years, we have always had this split; If you wanted a simple-to-use data transformation engine but not much data, use Power Query Dataflows. If you want scalable data ingestion, then use Azure Data Factory.

Best of Both Worlds

Now in Microsoft Fabric, We combine the best things from Power Query Dataflows and Azure Data Factory Data Pipelines into one stream: Data Factory. Data Factory ensures that you still have a simple-to-use and powerful transformation engine of Power Query for data transformation, but on the other hand, you also have the scalability of Data Pipelines and can build a control flow for execution of the ETL using the Data Pipelines. In other words, Data Factory is a state-of-the-art ETL software-as-a-service offering for Microsoft Fabric.

Elements of Data Factory

Combining these two services brings great features that make the Data Factory an ultimate ETL service. Here are some of those below;

Data Connectors

For an ETL (Extract, Transform, Load) system, one of the most important aspects is what sources the data can be fetched from. Data Factory offers hundreds of data connectors, enabling you to get data from sources such as databases, files, folders, software-as-a-service systems, etc.

It is also possible to create your connector if you are keen.

Dataflows

Dataflows are the heart of Data Factory. This is where you get the data from the sources, define the data transformation and prepare it in any shape needed, and finally load it into destinations. Dataflows use the Power Query data transformation engine and the user interface for creating it using the simple-to-use Power Query Editor online.

Power Query Editor online is not only powerful in the graphical interface, it also enables the developer to write code in M language, which is the data transformation language for Power Query.

To learn more about Dataflows, I suggest reading my article below.

Dataflows support a few destinations at the time of writing this article which are;

• Azure Data Explorer (Kusto)
• Azure SQL Database
• Data Warehouse
• Lakehouse

Data Pipelines

Although Dataflows are the main ETL component of the Data Factory, they can be enhanced when wrapped by a control flow execution component. This control flow execution component is called Data Pipeline. A Data Pipeline is a group of activities (or tasks) defined by a particular flow of execution. The activities in a Pipeline can involve copying data, running a Dataflow, executing a stored procedure, looping until a certain condition is met, or executing a particular set of activities if a condition is met, etc.

Data Pipelines can then be scheduled, and there is a monitoring tool to check the execution stage of the pipeline in addition to the activity-state-outputs where you can define what happens if a certain task fails or succeeds.

As mentioned, one of the most important activities that can be done in a Pipeline is the execution of a Dataflow. This is where Dataflows and Data Pipelines work together in their best way.

To learn more about Data Pipelines, read my article below;

Summary

Data Factory is an ETL-in-cloud solution that is the data integration workload of Microsoft Fabric. Data Factory is not a new product or service; it comes from many years of Microsoft data transformation tools and services. It is built on top of Power Query and Azure Data Factory. Data Factory uses two main components to deliver the best ETL scenarios possible; Dataflows and Data Pipelines. Dataflows are for the main get data, transform, and load process, and the Data Pipeline can control the rest of the execution with control flow activities.

I highly recommend reading the articles below to study more about Data Factory;

• What is Microsoft Fabric
• How to enable Fabric in your organization
• What is Lakehouse, and a sample Dataflow Gen2 created to load data into it.
• Getting started with Data Pipelines in Microsoft Fabric Data Factory
• Getting started with Dataflows in Microsoft Fabric Data Factory

The post What is Data Factory in Microsoft Fabric appeared first on RADACAD.

Follow Source

The post What is Data Factory in Microsoft Fabric appeared first on Microsoft Dynamics 365 Blog.

Microsoft Power Automate Button provides flexibility due to which users can now run/trigger the flow from their mobile from anywhere at any time. Earlier this used to be a time-consuming process for the users i.e. open Power Platform, search flow, and then run it.

But now, by using the ‘Power Automate’ app on Mobile, the users can easily search the Button and run the flow. Recently, we had a business requirement where Dynamics 365 CRM users can mark all their Orders as ‘Submit’ and on the click of ‘Order Submit,’ the existing pre-built integration logic will trigger and move Orders in another system. Usually, orders were submitted at any time as there was no specific time. But here they wanted to run flow at their convenient time.

Given below are the steps to execute the above business scenario.
Prerequisite: To click this button through the Mobile, you need to download the Power Automate app on your smartphone or tablet.

In the below steps we have shown how easily we can develop a Power Automate Button.

Step 1: Create the flow from outside the solution i.e. from Cloud Flow as shown below:

Step 2: In next step, give name to the Power Automate flow and select triggering event. As we want the flow to trigger on the click of button, select trigger as ‘Manually Trigger a Flow’ and then finally click on ‘Create’ button.

Step 3: We can also add Input parameters on the button that will take input from the user when the ‘Power Automate Button’ is clicked:

It will show parameters and their types i.e. text, Yes/No, Email, Date, Number. You can use them as per your need. Here, in our case we selected the input parameter as ‘Text’.

We can also update field properties like make them optional/required, add a dropdown list, or multi-select list. To update field properties, click on the menu icon and select the required option:

Step 4: In the below step we have retrieved all Orders which are created today and needs to be submitted. To retrieve Orders we have used Data verse ‘List rows’ action:

Step 5: Now in the next step we have added the Data verse ‘update a row’ action to update retrieved Order status as “Submit”.

Step 6: Save the flow.

Now our Button is ready to use and we can test it through the Phone ‘Power Automate’ app. All the Power Automate buttons will show under the Buttons section as shown in the below screenshot:

Step 7: To run the Button, just click on the ‘Submit Order’ button and a pop-up will appear with the parameter/ field that we created. Next, you just need to fill the fields and click on ‘Done’. Now the Power Automate flow will run.

Moreover, we can also allow another user to run the ‘Power Automate button’. And for this, we need to just share this button with a specific user.

Conclusion:

The Power Automate Button feature provides flexibility where users can run the logic just by tapping a button, thereby avoiding the time-consuming steps.

Please visit the Source and support them

The post How to trigger flows with Power Automate Button | Execute power automate from Canvas app button appeared first on Microsoft Dynamics 365 Blog.

The post Business Events in Dynamics 365 Finance and Supply Chain – How To appeared first on Ellipse Solutions.

Source

The post Business Events in Dynamics 365 Finance and Supply Chain – How To appeared first on Microsoft Dynamics 365 Blog.

In this step-by-step tutorial, learn how to use Microsoft Power Automate to create automated workflows. Streamline repetitive tasks and paperless processes with Microsoft Power Automate—so you can focus your attention where it’s needed most.

0:00 Introduction

1:43 How to get Microsoft Power Automate / Flow

3:29 Power Automate home page

4:04 Create a flow using a template

6:58 View and manage all of my flows

8:50 Create an automated flow from blank

10:05 Create an instant flow from blank

12:10 Create a scheduled flow from blank

14:28 UI and business process flows

16:00 Templates

16:29 Connectors

16:49 Wrap up

The post How to create Microsoft Power Automate – Tutorial for Beginners – step by step guid appeared first on Microsoft Dynamics 365 Blog.