Azure provides Speech Services that let developers add advanced speech features to achieve complex functionality, including Speech-to-Text. With Azure Speech Services, we can convert speech to text.

 In this blog post, let us check how the conversion from speech to text using Azure Speech Service in a Power Automate flow is done. The following steps can help achieve this requirement.

Recently, we got a requirement to transcribe audio attachments when an email is received with attachments in the shared mailbox and send back transcribed text.

Step 1: Create an ‘Automated’ flow

Create an ‘Automated’ flow using the trigger “When a new email arrives in a shared mailbox (V2)”

Step 2: Initialize the String variable

Add the ‘Initialize variable’ action to store the transcribed text of the audio attachment for further use.

Step 3: Initialize the Object variable

Add the ‘Initialize variable’ action to store the content of the audio attachment for further use.

Step 4: Get Attachments

Now, proceed to get the attached attachments of the received email. Utilize an ‘Apply to Each’ action to iterate through each attachment of an email and within that add a ‘Get Attachments (V2)’ action to get the current attachment of an email.

Expressions from the above image:

• triggerOutputs()?[‘body/attachments’]
• triggerOutputs()?[‘body/id’]
• items(‘Apply_to_each_Attachment ‘)?[ ‘id’]

Step 5: Validate the content type of the audio attachment

Add the ‘Condition’ action to validate that the content type of the audio attachment must be in WAV format. Inside this set the value of the ‘Body Content’ variable using the content type and content of the current attachment audio file.

Expressions from the above image:

• outputs(‘Get_Attachment_(V2)’)?[‘body/contentType’]
• outputs(‘Get_Attachment_(V2)’)?[‘body/contentBytes’]

Step 6: Convert Speech-To-Text

Add ‘HTTP’ action and do the following configurations,

• Method: Post
• URL: https://eastus.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/ v1?language=en-US

Note: Make sure to use your region code at the highlighted in the URL.

• Headers:
  • Accept: application/json;text/xml
  • Content-Type: audio/wav; codecs=audio/pcm; samplerate=16000;
  • Ocp-Apim-Subscription-Key: Azure API Key
  • Host: eastus.stt.speech.microsoft.com
  • Transfer-Encoding: Chunked
  • Expect: 100-continue
  • Body: ‘Body Content’ variable

Step 7: Get the text of the audio attachment

Add a ‘Parse JSON’ action to get the text of the audio attachment.

Schema:

 { "type": "object", "properties": { "type": { "type": "string" }, "properties": { "type": "object", "properties": { "RecognitionStatus": { "type": "object", "properties": { "type": { "type": "string" } } }, "Offset": { "type": "object", "properties": { "type": { "type": "string" } } }, "Duration": { "type": "object", "properties": { "type": { "type": "string" } } }, "DisplayText": { "type": "object", "properties": { "type": { "type": "string" } } } } } } } 

Expressions from the above image:

• body(‘HTTP_Azure_SpeechToText’)

Step 8: Append audio text in the variable

Add the ‘Append to string variable’ step and append the audio file text along with the file name.

We can use the above output for further use.

Conclusion:

By following these steps, you can effectively convert speech to text using Azure Speech Service in a Power Automate flow.

The post Convert speech to text using Azure Speech service in Power Automate Flow first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post Convert speech to text using Azure Speech service in Power Automate Flow appeared first on Microsoft Dynamics 365 Blog.

In Dynamics, managing access to sensitive data is handled through security measures such as role-based permissions. Security roles and access management play a significant role in ensuring that the right individuals have access to the appropriate information. To grant access to particular records, users with Share permissions typically navigate to the respective record and click on the “Share” button as shown below.

A common scenario arises when a sales manager needs to grant specific record access to a salesperson who doesn’t have the necessary permissions. The changes made by the sales manager may leave the salesperson unaware of their newly granted access, potentially leading to a loss in productivity. To resolve this issue, we can use access triggers introduced in Power Automate. These triggers activate whenever there is a change in user access for a particular record.

To improve this process, we can automate it by sending access notifications through email messages. By setting up a Power Automate flow, we can establish a notification system that triggers whenever access is granted, modified, or revoked for a particular user regarding specific records.

In this blog, we will utilize the example of a sales manager granting/modifying/revoking the permission of a salesperson in a lead record. To achieve this, we will need to create three different Power Automate flows, each of which is explained below.

1. Notify the user when Access is Granted for Lead records:

The GrantAccess action is triggered whenever full access, including Read, Write, Append, Append To, Delete, Share, and Assign permissions, is granted to the user for a specific record.

Let’s see how we can create a Power Automate flow for that:

Step 1: Create a Power Automate flow and select the trigger point as “When an action is performed”. Select the Catalog and Category as All, and Table as Lead. Select the Action name as GrantAccess.

Initialize the AccessMask and leadID Variable by clicking on add action and searching for initialize variable. Set the value for each variable as shown below:

• AccessMask = triggerOutputs()?[‘body/InputParameters/PrincipalAccess/AccessMask’]
• LeadID = triggerOutputs()?[‘body/InputParameters/Target/Id’]

Step 2: Validate the above variable values and retrieve Lead, Access Modified User, and Target User Information by using the Get a Row By ID action in Microsoft Dataverse connector as shown below:

• Lead = variables(‘leadID’)
• Access Modified User = triggerOutputs()?[‘body/InputParameters/PrincipalAccess/Principal/Id’]
• Target User Information = triggerOutputs()?[‘body/RunAsSystemUserId’]

Step 3: As we have retrieved all the necessary details, we can now send an email to the user informing them that they have full access to the record, as shown below. To send the email, we are using the Outlook connector. Essentially press on “Include an activity” and look for “Send an e-mail,” as illustrated underneath.

Now, enter the To as the primary email address of the target user and the Subject and Body as shown below.

2. Notify the user when Access is Modified for Lead records:

This flow triggers whenever specific access i.e. Read, Write, etc. is granted or revoked for a particular user under specific records.

When we look at the JSON output of the trigger action from the power automate, we can see the AccessMask in JSON data, which is the addition of all access values which has been given to the user as shown below.

Following are the access values for all permissions:

• Read: 1
• Write: 2
• Append: 4
• Append To: 16
• Delete: 65536
• Share: 262144
• Assign: 524288

Let’s say if we give a user Read and Write access, the AccessMask value will be 3. To check if the user has any specific permissions, we can use a basic calculation. First, divide the AccessMask value by the permission value (either Read or Write shown above). At that point, apply the modulo operation by 2 (which is nothing but the leftover portion returned after isolating by 2). If the remainder is 1 or greater than 1, the permission is granted. If the remainder is 0, the permission is not granted.

Imagine you have a user with Read and Write access, you would get the Access Mask as 3. Here’s how you can identify if specific permissions (Read or Write) are granted to the user.

1. Access Mask Value: 3 (this means both Read and Write permissions are granted)
2. Permission Values:
   • Read: 1
   • Write: 2

To check if each permission is granted, follow these steps:

Step-by-Step Calculation

For Read Permission:

1. Divide the Access Mask Value by the Read Permission Value:

• 3÷1=3

2. Apply the Modulo Operation (remainder when divided by 2):

• 3 modulo 2=1

3. Interpret the Result:

• As the result is 1, the Read permission will be granted.

For Write Permission:

1. Divide the Access Mask Value by the Write Permission Value:

• 3÷2=1.5

2. Apply the Modulo Operation (remainder when divided by 2):

• 5 modulo 2=1.5

3. Interpret the Result:

• Since the result is greater than 1, the Write permission is granted.

So, in this case, both Read and Write permissions are granted to the user based on the calculated values. This process helps us determine whether specific access permissions are granted or not for a given Access Mask value. Let’s implement this in the Power Automate and see how we can check if the permission is granted or not.

Step 1: The triggered step and variable declaration will be the same as we have used in Step 1 of GrantAccess flow; the only change is that the action name will be ModifyAccess.

Step 2: Initialize boolean variables for all access permissions and set the respective expressions as shown below:

• Read Permission Check Equation:

IsReadPermissionGranted = if(equals(mod(div(variables(‘AccessMask’), 1), 2), 1), true, false)

• Write Permission Check Equation:

IsWritePermissionGranted = if(equals(mod(div(variables(‘AccessMask’), 2), 2), 1), true, false)

• Append Permission Check Equation:

IsAppendPermissionGranted = if(equals(mod(div(variables(‘AccessMask’), 4), 2), 1), true, false)

• Append To Permission Check Equation:

IsAppendToPermissionGranted = if(equals(mod(div(variables(‘AccessMask’), 16), 2), 1), true, false)

• Delete Permission Check Equation:

IsDeletePermissionGranted = if(equals(mod(div(variables(‘AccessMask’), 65536), 2), 1), true, false)

• Share Permission Check Equation:

IsSharePermissionGranted = if(equals(mod(div(variables(‘AccessMask’), 262144), 2), 1), true, false)

• Assign Permission Check Equation:

IsAssignPermissionGranted = if(equals(mod(div(variables(‘AccessMask’), 524288), 2), 1), true, false)

Step 3: Now we have all permission values as Boolean. We can check if the value is true, and then the access is granted; otherwise, the access is revoked as shown below:

• Read: @{if(variables(‘IsReadPermissionGranted’), ‘Granted’,’ Revoked’)}
• Write: @{if(variables(‘IsWritePermissionGranted’), ‘Granted’,’ Revoked’)}
• Append: @{if(variables(‘IsAppendPermissionGranted’), ‘Granted’,’ Revoked’)}
• Append To: @{if(variables(‘IsAppendToPermissionGranted’), ‘Granted’,’ Revoked’)}
• Delete: @{if(variables(‘IsDeletePermissionGranted’), ‘Granted’,’ Revoked’)}
• Share: @{if(variables(‘IsSharePermissionGranted’), ‘Granted’,’ Revoked’)}
• Assign: @{if(variables(‘IsAssignPermissionGranted’), ‘Granted’,’ Revoked’)}

3. Notify the user when Access is Revoked for Lead records:

This flow triggers whenever all access of the user has been removed from the specific record.

The flow is almost similar to the Grant Access flow, apart from some modifications mentioned below:

1. The Action name would be RevokeAccess
2. Retrieve the Target user record by providing the Table name as “User” and Row Id from Trigger Outputs i.e. “triggerOutputs()? [‘body/InputParameters/Revokee/Id’” as shown below
3. The email needs to be modified as shown below

Conclusion:

By following the steps for creating Power Automate flows to notify users about access changes, organizations can not only improve productivity but also strengthen security measures by maintaining clear visibility and control over data access.

The post Exploring Access Management using Power Automate Flows in Dynamics 365 first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post Exploring Access Management using Power Automate Flows in Dynamics 365 appeared first on Microsoft Dynamics 365 Blog.

Receipt processing is a prebuilt artificial intelligence model available in Power Automate. It’s designed to analyze receipts using cutting-edge optical character recognition (OCR) technology. This model can understand both printed and handwritten text on receipts. Once it reads a receipt, it extracts important information such as the store’s name and address, the transaction’s date and time, and a detailed list of items purchased. For each item, it identifies the name, price, quantity, and total cost. Additionally, it calculates the subtotal (the total before tax), the tax amount, any tip included, and the final total spent. This helps streamline tasks like expense tracking and management.

Let’s delve deeper into this practical example for a better understanding:

At a local general store, the owners use Dynamics 365 CRM to keep customer information. However, keeping track of customers’ purchases and calculating daily profits has been difficult. They used to manually enter each purchase into a record, export it to Excel, and then figure out the daily profit. This process took a lot of time and often had mistakes.

To make things easier, they decided to use the receipt processing feature in Power Automate. Now, when a customer buys something, they just upload the receipt into the system. The receipt processing model automatically extracts important details like items bought, their prices, and the total amount spent. This data is then automatically entered into an Excel spreadsheet.

Implementing the described scenario using Power Automate

A custom entity named “Customers” has been established, containing fields for customer details such as name, phone number, and address. Additionally, a “Receipt” field has been incorporated for uploading receipt images or files.

Currently, our Power Automate flow is triggered by a modification of a row, as the receipt upload in the form can only occur after the record is created. We’ve specified the customer’s table name in the parameters.

After retrieving the record, we need to download the associated file. To accomplish this, we will add a “Download a file or an image” action immediately after the trigger action. We’ll pass the extracted record ID to this action and specify “receipt” as the column name from which the file will be downloaded.

After getting the file, we’ll use a tool to extract information from the receipts. If the document is big and has just one receipt, we’ll tell the tool which page the receipt is on. This enhances cost-effectiveness and improves operational efficiency.

Note: Suppose there are receipts on different pages: one on page 2 and another spanning pages 3 and 4. If you specify ‘2’, the tool will only gather information from the first receipt. Choosing ‘3-4’ means it will only extract info from the first page of the second receipt. If you choose ‘2-4’, it will collect details solely from the first receipt, ignoring the second one.

To enter the extracted information into an Excel sheet, we’ll link the output parameters to the columns of our created table in Excel Online. The output parameters from the Receipt extraction model include the purchased item name, quantity, price, merchant’s name, address, total amount, subtotal, tip, tax, and more. We’ll organize this data in the Excel sheet according to our table columns.

Now that our flow is set up, we’ll test it by uploading the following receipt in the customer’s entity form.

The flow was activated when a modification was made to a customer entity’s record. The information from the receipt image was successfully extracted and entered into the system according to the flow’s instructions. You can now compare the values of those entries with the details from the receipt image provided above.

Conclusion

Our flow successfully automated the process of extracting information from a receipt uploaded to a customer entity’s record. By triggering the flow upon modification of the record, we ensured that the receipt details were accurately captured and entered into the system. This streamlined the data entry process and provided a reliable way to compare the entered values with the original receipt image. Overall, the flow showcased the efficiency and precision of automating repetitive tasks with Power Automate.

Empower Your Dynamics 365 CRM with Our Next-Gen AI Expertise!

Step into the future of app development with our Copilot-enabled Power Platform solutions, Azure OpenAI Sales Companions, and Copilot Studio Developments. Contact crm@inogic.com to unlock business success with AI integration.

The post Automate Receipt Data Extraction and Entry into Excel with Power Automate AI Model first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post Automate Receipt Data Extraction and Entry into Excel with Power Automate AI Model appeared first on Microsoft Dynamics 365 Blog.

As Microsoft is providing us more flexibility with Power Automate (MS Flow), now we can retrieve List of solution details and their components directly within Power Automate flows.

Recently, we got a requirement to retrieve the list of solutions and their components from specific environments and store this information in an Excel file on SharePoint.

We can achieve this using Solution and Solution Components entity records in Dynamics CRM.

Below are the steps to achieve this requirement.

Step 1: Initialize the Array variable

This array variable should include the details of the solution component types you want to retrieve from the solution, as shown in the screenshot below.

The above array contains the following details of the solution component types:

• ComponentType – The type value of the component from the documentation.
• EntityName – The logical name of the component type.
• FilterRowName – The field name to filter the component type.
• SelectColumn – The field name to filter the component type.

You can find all solution component types information in Microsoft Documentation

Step 2: Retrieve solutions

Add the ‘List rows from selected environment’ step to retrieve the solutions from the specific environment. Use a filter query to retrieve the visible solutions and exclude the default solution.

Step 3: Retrieve Solution Components

Now, proceed to retrieve the solution component for the previously obtained solution. Utilize an ‘Apply to Each’ step to iterate through each solution, and within that, add a ‘List rows’ action to retrieve the solution component using the filter rows.

Step 4: Filter Array step to check the Component Type

For each solution component, implement an ‘Apply to Each’ loop. Inside this loop, use a Filter Array step to check that the Component Type of the current solution component matches the type specified in the array variable we set up earlier.

Expressions from the above image:

• variables(‘SolutionCompentSummary’)
• @item()[‘ComponentType’]
• items(‘Apply_to_each_Solution_Components’)?[‘componenttype’]

Step 5: Retrieve Solution Components Summary

Add the ‘List rows’ step to retrieve the solution component if the Component Type matches and add a row into the Excel table.

Expressions from the above image:

• length(body(‘Filter_Solution_Component_Summaries’))
• body(‘Filter_Solution_Component_Summaries’)[0][‘EntityName’]
• body(‘Filter_Solution_Component_Summaries’)[0][‘FilterRowName’]

Expressions from the above image:

• items(‘Apply_to_each_Solutions’)?[‘uniquename’]
• items(‘Apply_to_each_Solutions’)?[‘createdon@OData.Community.Display.V1.FormattedValue’]
• items(‘Apply_to_each_Solutions’)?[‘version’]
• items(‘Apply_to_each_Solutions’)?[‘ismanaged@OData.Community.Display.V1.FormattedValue’]}
• outputs(‘List_of_Solution_Component_Summary’)?[‘body/value’][0]?[body(‘Filter_Solution_Component_Summaries’)[0][‘SelectColumn’]]
• concat(toUpper(take(replace(string(outputs(‘List_of_Solution_Component_Summary’)?[‘body/value’][0]?[‘@odata.type’]), ‘#Microsoft.Dynamics.CRM.’, ”), 1)), toLower(skip(replace(string(outputs(‘List_of_Solution_Component_Summary’)?[‘body/value’][0]?[‘@odata.type’]), ‘#Microsoft.Dynamics.CRM.’, ”), 1)))

Conclusion:

By following these steps, you can retrieve Solutions and their component details using Power Automate flow.

From customizing Microsoft Dynamics 365 to developing Copilot-enabled Power Platform Apps, our outsourced development services ensure top-notch solutions tailored to your needs. Let our experts handle the technicalities while you focus on your core business. Email us at crm@inogic.com to get started today.

The post List solution details and their components using Power Automate Flow first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post List solution details and their components using Power Automate Flow appeared first on Microsoft Dynamics 365 Blog.

The tools of AI Builder help you find important information in text. They organize this info into categories that make sense for your business needs.

There are two types: prebuilt and custom. Prebuilt ones are ready to use without any extra work. They’re great for lots of common tasks. Custom ones need you to train them with your data and settings. This way, you can make a model that’s perfect for what you need.

Practical Example: Making Appointments Easier with Automated Data Handling

Imagine running a small doctor’s office. Patients fill out a form on your website with their name, phone number, city, email, and when they want an appointment. With AI Builder in Power Automate, the system automatically collects and saves this info from the forms present on the website.

As patients send their forms, Power Automate quickly grabs the important details and stores them in a file or your CRM system. Later, when it’s time to schedule appointments, you can easily find the patient’s info, contact them, and sort out their appointments.”

Extract Data from Text and Input into Excel Spreadsheet

We’ll create a manual-triggered flow in Power Automate to demonstrate using AI Builder’s entity extraction model. This flow will include a Text Input parameter.

Now, next to the initial triggered action, add an AI Builder action. From the available AI Builder actions, select “Extract entities from text with the standard model.”

This action requires two parameters: the first one is the language, and the second one is the text. You can pass a file as well from the trigger action, but documents cannot exceed more than 5,000 characters.

As we proceed to input data into the Excel file, a table has been prepared with two columns: one for the type of entity and the other for its respective value. This model will provide outputs such as entity value, entity type (including person’s name, phone number, email, city, date, etc.), confidence score, character length, and starting location.

Now that the flow is set up, we can proceed with testing it. To do this, I’m passing the content of an email as input to the manually triggered action. In the email content, you’ll find information such as the patient’s name, phone number, address, and preferred date, as shown in the screenshot below.

After executing this flow, you’ll find the results in the Excel file. Unlike the key phrase extraction model, this model is more advanced as it allows you to categorize the detected text. In contrast, key phrase extraction simply extracts key phrases from the text or file. For further understanding of the key phrase extraction model and its application, you can refer to the blog titled “Understanding key phrase extraction in power automate for text analysis”.

Conclusion

We’ve successfully demonstrated the implementation of a Power Automate flow utilizing an entity extraction model. Through a practical example of appointment scheduling at a medical clinic, we showcased how this technology efficiently extracts and organizes relevant data from text inputs. By automating the extraction process, businesses can streamline their workflows, enhance data accuracy, and improve overall efficiency. With the ability to categorize extracted information, AI Builder’s entity extraction model offers a powerful solution for various text analysis tasks.

The post Streamlined Text and Document Categorization with Entity Extraction in Power Automate first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post Streamlined Text and Document Categorization with Entity Extraction in Power Automate appeared first on Microsoft Dynamics 365 Blog.

To utilize this prebuilt model within Power Automate, refer to the documentation titled “Using the Key Phrase Extraction Prebuilt Model in Power Automate” for detailed instructions and guidance on implementation.

Note: The format for data input is limited to a maximum of 5,120 characters per document when using the key phrase extraction prebuilt model.

Use Case: Extracting Key Phrases from Email for Meeting Preparation

Scenario:

You have sent an email to a client detailing your product features that can fulfill their requirements. Now, you want to automatically extract key phrases from that email and store them in a spreadsheet to prepare for an upcoming meeting or call with the client.

Solution Overview:

When the client responds to your email or when you manually trigger the process, Power Automate will retrieve the email content, extract key phrases using AI Builder’s Key Phrase Extraction model, and then update a spreadsheet with the extracted key phrases for easy reference during the scheduled meeting or call.

Let’s explore how we can implement this functionality using Power Automate.

To trigger the Power Automate flow when a new email message record is created in Microsoft Dynamics 365 CRM, set the change type to ‘added’, the table name to ’email message’, and configure the scope at the ‘organization’ level based on your specific needs.

Next, we’ll incorporate the Key Phrase Extraction prebuilt model in our flow to extract key phrases from the email. We’ll map the email message description to the text field of the Key Phrase model for analysis.

To store the extracted key phrases along with email details in an Excel sheet using the “Excel Online (Business)” connector, I’m creating a table with columns for Subject, Description, and Key Phrases.

Now that the table is set up, we’ll proceed to add it as the next action in our flow and map the fields accordingly to populate the Excel sheet with the email subject, description, and extracted key phrases.

Upon adding this action, Power Automate will automatically incorporate a “For Each” loop in the flow, which will iterate through each extracted key phrase from the email description. This loop ensures that the subsequent actions are applied to each key phrase individually. With this setup, our flow is now complete. Let’s save it and proceed to testing.

To test our flow, we’ve created an email activity record in Dynamics 365 CRM. Below is the record details and its description. This email contains points about the product features we plan to discuss with the client during an upcoming scheduled meeting, focusing on fulfilling the client’s requirements.

Once we create the email, it will trigger our flow to extract key phrases from its description and add them to our Excel table. This automated process helps organize and capture important topics discussed in the email for further analysis or action.

Conclusion

We’ve successfully implemented an automated workflow using Power Automate and Dynamics 365 CRM to extract key phrases from email descriptions and store them in an Excel table. This streamlined process allows us to efficiently capture and analyze important topics discussed in client communications, enabling better preparation and organization for client meetings and engagements.

The post Understanding Key Phrase Extraction in Power Automate for Text Analysis first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post Understanding Key Phrase Extraction in Power Automate for Text Analysis appeared first on Microsoft Dynamics 365 Blog.

Utilize the prebuilt business card model to extract details from images of business cards. Upon detecting a business card in the image, the AI model automatically extracts key information, including the individual’s name, email, address, company, job title, and contact numbers. Once extracted, this data can be used efficiently for various purposes, streamlining processes and eliminating manual data entry tasks.

Note: Currently, the prebuilt business card reader supports extraction in English and Japanese languages exclusively.

Additionally, images must be in JPG, PNG, BMP, or PDF format. Furthermore, the size of the image file should not exceed 50 MB. By ensuring that your images meet these requirements, you can effectively utilize the business card model for accurate data extraction.

Using Business Cards to Extract Data

To create a flow that utilizes the business card reader with a basic example, we’ll set up a manual trigger and include an action to upload a sample card file. Then, we’ll check if it can successfully create a contact record in our Dynamics 365 CRM.

First, let’s set up the flow:

1. Manual Trigger: Start by adding a trigger that is manually initiated. This will allow you to trigger the flow whenever you’re ready to upload the sample card file.
2. Upload File: Add an action to upload the image file. You can use a suitable action depending on where your file is stored, such as “Get file content” if it’s stored in a cloud storage service like OneDrive or SharePoint.
3. Business Card Reader: Next, add an action to use the business card reader model. Choose the appropriate action provided by AI Builder for extracting information from the uploaded image.
4. Create a Record in Dynamics 365 CRM: Finally, add an action to create a contact record in your Dynamics 365 CRM. Map the extracted information from the business card reader action to the corresponding fields in the contact record.
5. Save and Test: Once you’ve set up the flow, save it and give it a name. Then, manually trigger the flow and upload the sample card file. Check if the flow successfully extracts the information and creates a contact record in your Dynamics 365 CRM.

To integrate the extraction of information from a business card into your flow, simply search for the “Extract information from business card” action in the actions list and add it after triggering your flow.

By keeping the file type detection set to automatic, the action will efficiently process the uploaded card file. Ensure to specify the uploaded card file in the “Business card” field, typically sourced from the previous action where the file was uploaded.

It’s advisable to implement validations before creating a record in your Dynamics 365 CRM, especially considering scenarios where the AI might not detect all the required data. In the screenshot provided, we will validate the last name data from the card, recognizing it as a mandatory field for creating a contact record. This precautionary step ensures that essential information is present before proceeding with record creation, reducing the risk of incomplete or inaccurate record creation in your Dynamics 365 CRM system.

Next, connect all the field values you wish to fill after the AI model detects them. This includes name, contact details, email, job title, company name, and address details.

Now that the flow is complete, we can test it by manually uploading an image file in the Card Input field, as shown in the below screenshot.

Although it may take some time for the AI model to detect and extract data from the uploaded file, the process ultimately saves a significant amount of time compared to manual entry.

Conclusion

We have successfully created a Microsoft Power Automate flow to extract information from a business card and generate a contact record from it. This efficient process not only saves time but also allows end-users to focus on more critical tasks. Importantly, creating this flow doesn’t require the user to be a technical expert, showcasing the accessibility and user-friendly nature of Power Automate. With this automated workflow, tedious manual data entry tasks are minimized, enabling users to allocate their time and resources more effectively.

The post Utilize the Power of Prebuilt Business Card Reader Model in Microsoft Power Automate first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post Utilize the Power of Prebuilt Business Card Reader Model in Microsoft Power Automate appeared first on Microsoft Dynamics 365 Blog.

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.

I needed one URL that would trigger on “GET” and “POST” methods. Only one time it will trigger the “GET” method to validate logic and after that, it will call for the “POST” method to process some response. Below is the approach that allowed us to fulfill the client’s requirements seamlessly.

1. Create a solution in https://make.powerapps.com/where you have to add your Power Automate (Ms Flow)

2. In the solution click on the “New” button & select Flow as shown in the below image. It will redirect you to the Power Automate (MS Flow) window as shown in the following image.

3. Now we have to Search for the “When an HTTP request is received” Trigger point in our newly created Flow & from the search result select “When an HTTP request is received” and select “Who can trigger the flow” from the dropdown as per your requirement configure “Who can trigger the flow” based on your needs. Set the method as “GET” and give your flow a name. Finally, click on “Save” to obtain the “HTTP POST URL”.

4. Once saved, you’ll receive an HTTP POST URL, as illustrated in the image below. Now I am using this URL as the endpoint. This ensures that whenever it is triggered, your flow will also be triggered, regardless of whether the request is a “GET” or “POST“.

5. Next, add the “Initialize Variable” action to create variables. It will store the data coming into the Body.

6. When the “GET” method is called then Body will be blank, we will get a result from query string parameters however in the “POST” method response will come in Body. So, to handle both scenarios I have added the condition to check If Data is null then it should move further and take query string parameters and return them in the response as well as update that Power Automate from the “GET” method to “POST” else it will direct return the response.

Whenever any Power Automate gets created those are stored in the “workflow” entity. So, I tried to find my Power Automate using ODATA and I got its ID, name, and other details. It stores all Power Automate steps in one field “clientdata” in JSON format. So, to update from “GET” to “POST” we need to follow the below steps.

Now in Power Automate, we specified the table (entity) name as “Processes” which is the display name of the “Workflow” entity, and entered the ID of our flow in the “Row ID” field. we also need to retrieve the method stored in the “clientdata” attribute column. Therefore, select “clientdata” in the “Select columns” option. Also, set the variable “RecordData” using the “Body” output of the “Get row by ID” action.

7. Following this, use the “Compose” action, where the input will be modified by substituting “GET” with “POST” in the aforementioned JSON.

8. The subsequent step involves parsing the JSON, which means converting the JSON string into an object format. It’s essential to input the correct schema, as illustrated in the image provided.

9. The final step involves updating the previously retrieved process record. Modify the “clientdata” column to reflect the updated “clientdata”, wherein the method has been changed to “POST“.

10. After the record is updated, the modified JSON will resemble the image below.

Conclusion

In conclusion, the method outlined above demonstrates how you can dynamically alter the flow’s method from “GET” to “POST”. This is particularly useful when there’s a requirement for your flow to be triggered once using the “GET” method and subsequently, for all future triggers, to operate using the “POST” method.

The post How to configure a trigger to handle both GET and POST requests effectively using Power Automate first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post How to configure a trigger to handle both GET and POST requests effectively using Power Automate appeared first on Microsoft Dynamics 365 Blog.

A common software development hurdle is the scarcity of time. While it’s widely acknowledged that merely increasing the number of developers doesn’t necessarily boost productivity, the inclination toward adopting new tools and technologies persists. The goal is to minimize code writing, expedite the development process, reduce susceptibility to bugs, and adhere to standards, especially in terms of security. Microsoft Power Platform adeptly addresses these needs in professional software development.

Microsoft Power Platform offers a wealth of functionality with minimal coding, facilitating easier and faster development. Traditional languages like C# and TypeScript can be employed for extensions, deployable to the cloud or on-premises servers if necessary. Emphasizing “low-code” essentially translates to writing less code, streamlining maintenance, support, and upgrades, thereby freeing up time for innovative feature development.

Microsoft Power Platform has four primary components:

• Power Apps is a no-code/low-code way to build canvas-based or model-based apps.
• Power BI is a set of tools for data analysis and visualization.
• Power Automate is a template-based application for building workflows and automating key tasks.
• Power Pages is a low-code hosting SaaS platform, perfect for crafting and launching business websites
• Power Virtual Agents (Copilot Studio) is a renovated solution for creating AI-powered chatbotsto help your employees and customers.

The Excellence or let’s say Power of Power Platform

Unlike conventional software libraries that require constant updates to evade deprecations and security vulnerabilities, Microsoft Power Platform excels in staying up-to-date with security patching. Additionally, it seldom removes features, providing ample notice before doing so.

Microsoft Power Platform developer tools empower professionals to craft more effective business solutions than ever before. Development accelerates, applications become more secure, and deployment occurs within managed environments that enforce organizational policies and champion best practices.

Developers engaging with the platform should grasp its fundamental offerings. For a comprehensive overview of each core product area and key extensibility points, refer to this link: https://learn.microsoft.com/en-us/power-platform/developer/get-started.

To evaluate the business value of Power Platform solutions across various spectrums, visit https://learn.microsoft.com/en-us/power-platform/guidance/adoption/business-value.

What’s the Hype around Copilot?

Now, if you’re skeptical about the buzz surrounding “low-code,” especially with the rise of AI and Copilot’s natural language app building, consider Microsoft Copilot Studio.

Note: Copilot integrates Power Virtual Agents capabilities, allowing the creation of powerful AI-powered copilots for various tasks.

These tasks range from answering common questions to resolving complex issues through intricate conversations. You can access Copilot Studio as a standalone web application or as an integrated application within Teams, providing comparable functionality in both instances. Learn more about Copilot Studio at this link: https://learn.microsoft.com/en-us/microsoft-copilot-studio/fundamentals-what-is-copilot-studio.

For insights into Copilot Studio’s use cases and how it accelerates development processes, watch this informative 34-minute video: https://youtu.be/WKOJOOGdj2o?si=v5BTYOtkZmLIp9pR.

The demand for application development is undeniably massive and growing. Developers are finding ways to expedite their processes by creating new apps, modernizing existing ones, or incorporating innovations with Copilot’s AI capabilities.

For additional information on Copilot’s users and insights into generative AI at work, refer to the Microsoft Worklab’s Work Trend Index: https://www.microsoft.com/en-us/worklab/work-trend-index/copilots-earliest-users-teach-us-about-generative-ai-at-work.

Commencing a development project involves critical decisions on technology, data access layers, security measures, and app scalability. The chosen level of abstraction often dictates development speed, with trade-offs between productivity, flexibility, and cost. Leveraging Microsoft Azure services, such as Microsoft Azure API Management, is a prime example of reaping benefits in this context.

Curious to know more about Microsoft Azure API Management? Refer to this link for a quick overview and essential points https://learn.microsoft.com/en-us/azure/api-management/api-management-key-concepts

Crafting business applications can get pretty intricate, considering the multitude of factors like UI design, storage, security, compliance, and scalability. But fear not, because Microsoft Power Platform steps in to make this whole process a breeze.

Imagine whipping up responsive and user-friendly applications once and unleashing them across various platforms, be it desktops or mobile devices. The secret sauce? Reusable UI components built with React, neatly arranged using a drag-and-drop interface. And don’t worry about limiting them to a single application – with Microsoft Visual Studio Code, you can develop and deploy React components for one app or share them seamlessly across multiple projects via a centralized repository.

Deployment is a walk in the park too. ‍

Packages containing metadata components, compiled code, and data import files can be effortlessly deployed as apps. Need to go mobile? No problem. Deploy canvas apps as native mobile applications to your users via Microsoft Intune, Visual Studio App Center, Google Play Store, or Apple Business Manager.

Oh, and the perks don’t stop there.

Picture this: Native offline support with a local MySQL database, automatically storing data operations to replay them once you reconnect to the network. Testing? Covered. The Test Engine uses Playwright to run UI tests as part of your automatic testing pipelines.

Want to kick things up a notch in automation?

Enter Microsoft Power Platform CLI (A one-stop developer CLI that empowers developers and ISVs to perform various operations) your go-to for automating solution development, deployment, and environment management. It syncs seamlessly with Azure PowerShell, Microsoft Azure Pipelines, or GitHub actions.

And hey, if public-facing websites are on your to-do list, Power Pages are your friend. Create them swiftly and polish them up with Visual Studio Code. These sites, backed by Azure-deployed ASP.NET, come with automatic CDN and caching support. Plus, you can flex your creative muscles with the built-in Web API, complete with a configurable security provider, to craft intricate single or multi-page applications.

Data is scattered across your organization, and external services play a crucial role in business processes. For seamless business solutions, integration and connectivity are key, and Microsoft Power Platform steps in to simplify the process.

Ally = Microsoft Visual Studio à True

Unlocking a library of over 1,000 connectors, you can create event-driven orchestrations without the hassle of Azure subscription setup and deployment. Microsoft Visual Studio becomes your ally, allowing you to craft ASP.NET Web APIs that can be easily deployed as custom connectors. Debugging? A breeze with dev tunnels, courtesy of Visual Studio’s Microsoft Power Platform Connected Services configuration.

Visual Studio Installation Guide – https://learn.microsoft.com/en-us/visualstudio/install/install-visual-studio?view=vs-2022

Manage your Fragmented Data with Dataverse and AI

For real-time analytics within OneLake, leverage Dataverse Synapse Link and Dataverse Link to Microsoft Fabric data. Dataflows in Microsoft Power Platform utilize Power Query to import or synchronize data from diverse sources.

Explore the newly introduced Microsoft Fabric and witness how it revolutionizes data access, management, and action through a unified, AI-powered platform.

Now, onto the data platform as a service. Storing data securely, efficiently, and at scale is a breeze with Microsoft Power Platform utilizing Microsoft Dataverse (A data storage management used by business applications). It’s a cloud-based data platform, robustly built upon Azure, offering familiarity with Microsoft Azure SQL, Cosmos DB, Data Lake, and Azure Blob Storage. Data, whether relational, Azure Blob or unstructured, is metadata-driven, facilitating highly contextual access. Fully functional apps can be automatically generated using this metadata, with AI enabling natural language queries.

Uptime guarantees and monitoring tools provide complete visibility without the need for additional logging and monitoring solutions. The Dataverse SQL endpoint seamlessly generates visually captivating Microsoft Power BI dashboards and reports.

Extend Dataverse with custom business logic using C# and create custom APIs within the platform.

Native integration with Microsoft Azure Service Bus allows easy extension with Azure Functions, Event Hubs, and Event Grid. Virtual tables enable surfacing, querying, and linking of non-Dataverse data sources. Built-in audit log capabilities and long-term data retention features allow tracking changes without added development or management. Dataverse search offers a fast, AI-powered way of finding data and documents.

Moving on to native AI support

Configure and deploy conversational bots using Azure Bot Service. Train complex AI models for document, image, and sentiment recognition, easily deploying them in business applications. Microsoft Copilot Studio facilitates the creation of natural language conversational AI copilots through a graphical UI, trained for internal or external scenarios. Copilot plugins, built using OpenAI connectors and prompt engineering, can be seamlessly added to business applications for a user-friendly natural language interface.

Copilot in Power Apps and other Power Platform tools helps developers by letting them ask questions and seek information effortlessly. It makes the developer experience more interactive and streamlined. For more details, check out the article here: https://www.linkedin.com/pulse/power-platform-ai-apps-copilot-amber-weise/.

For all your security concerns related to Copilot accessing your data to provide relative responses, go through this https://learn.microsoft.com/en-us/power-platform/faqs-copilot-data-security-privacy

If you are seeking Power Platform Development as a service to unlock advanced functionalities

Or access a dream team for Power Platform projects? Look no further than Inogic Professional Services, your go-to partner for unleashing the full potential of your data and streamlining workflows.

With a pool of over 150+ Power Platform experts boasting 15+ years of industry experience, Inogic is your ideal companion for all Power Platform and Dynamics 365 requirements. Here’s what Inogic brings to the table:

Power Platform Professional Services :

Elevate your business with Inogic’s Industry Experience and Expertise in Power Platform Development.

• Power Apps (Canvas or Model based)
• Power Pages
• Power BI
• Power Automate

AI Solutions Professional Services:

Make your Business AI-enabled and Future Ready with latest AI solutions.

• Azure OpenAI for business processes
• Copilot-enabled AI Apps for Dynamics 365 and Power Platform

Development Services:

Empower your business to thrive in its core areas while our Dynamics 365 Resource Augmentation allows seasoned experts to handle your development needs with precision and proficiency.

• Outsourced Development
• Dedicated FTEs
• ISV/Partnership App Development
• ODC (Offshore Development Center)
• Data Migration
• Integration to Dynamics

Techno-Functional Consultancy: to maximize your sales potential, nurture lasting customer relations, and accelerate processes.

• Dynamics 365 Sales, Customer Services, or Field Services expertise.

Inogic offers an array of cutting-edge innovations to make your development efficient, scalable, and future-proof.

Connect with us today at crm@inogic.com or visit Inogic.com/Services to discover how we can elevate your organization’s capabilities. Your journey to harnessing the Power Platform and Dynamics 365 advanced feature packed development starts here!

The post Master Microsoft Power Platform Development: A Developer’s Cheat Sheet in 2024 first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post Master Microsoft Power Platform Development: A Developer’s Cheat Sheet in 2024 appeared first on Microsoft Dynamics 365 Blog.