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.

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.

As a Developer working on a project, I always create an unmanaged solution and then create a unique Publisher so that a unique prefix can be used for the tables. But sometimes, by chance when I create a table outside the context of the solution it resides inside the default solution with the prefix new which is quite a frustrating and hectic task.

Also, when I work with my team and everyone works on different projects that need different solutions with different prefixes like, my solution should contain the prefix ‘jack’ and for the other user, the prefix should be like ‘temp’. But sometimes those solutions end up with having the default prefix i.e., ‘’new’.

As a solution to it, Microsoft has introduced a game-changing feature recently – ‘Set the Preferred Solution.’ With this feature, you can designate your unmanaged solution as the preferred one, ensuring that any new elements you create or modifications you make will reside in your chosen solution.

Here’s how to enable this feature:

Access the Power Platform Admin Center:

Start by navigating to admin.powerplatform.com. Select your environment and go to the ‘Features’ tab in the settings.

Enable the Preferred Solution Feature:

Once in the ‘Features’ tab, enable the ‘Preferred Solution‘ feature. This is the foundation of the entire setup.

With the ‘Preferred Solution’ feature enabled, you’re now ready to set your chosen solution as the preferred one in Power Apps. Here’s how to do it:

Access Power Apps Studio:

Head to make.powerapps.com and go to the ‘Solutions’ tab.

Select Your Preferred Solution:

By default, the ‘Default Solution’ is set as the preferred one. Click on the ‘Manage’ button, and you’ll be able to choose your unmanaged solution as the preferred option. For example, you can create an unmanaged solution named ‘Customizations’ and select it as your preferred solution.

With these settings in place, you’re ready to benefit from the preferred solution feature. Now, when you create a table or work on other components, they will automatically be housed in your chosen solution, complete with your unique prefix.

Now, after setting the Preferred Solution as Customizations which contains the prefix ‘jack’, I created one table with some columns, and automatically instead of using the Default one’s prefix i.e., new it took ‘jack’ as the prefix and that’s how my issue was solved. The same was reflected for the other developers in my team as well and they were able to seamlessly manage their own preferred solution with their Publisher and prefix for different projects which made our task very easy and efficient.

Similarly, when you create different assets such as forms, views, components, etc., the unique prefix from the Preferred Solution will be applied automatically.

That’s how the feature works for the assets mentioned above. Also, if you want to add the Power Automate flows and the Canvas Apps in the preferred solution, you can enable the options provided in the below screenshot.

Conclusion

This game-changing feature not only streamlines your development process but also ensures that your work reflects your unique branding and organization’s needs. Say goodbye to the ‘new’ prefix and make Power Apps your own with the preferred solution feature.

The post Set Your Preferred Solution in Power Apps for Enhanced Customization first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post Set Your Preferred Solution in Power Apps for Enhanced Customization appeared first on Microsoft Dynamics 365 Blog.

For 15+ years, Inogic has been assisting clients with its Dynamics 365 professional services to get the most from their CRM investments to develop stronger customer relationships, enhance productivity, optimize the sales process, and reduce operational expenses. We combine our deep expertise in Microsoft Dynamics 365 and Power Platform with experience in procedures, project methodology, and IT architecture. If a requirement cannot be met with the out-of-the-box features, our Dynamics CRM Techno-functional consultants create simple, customer-specific apps to address the gaps. In this Part 1 of a two-part series on Inogic Professional Services, we discuss how Inogic Techno Consulting Services aims to provide expert solutions in the nine areas listed below.

Dynamic 365 Sales

Gain the first-mover edge over your competitors with a well-crafted digital transformation strategy that includes Microsoft Dynamics 365 for Sales. Inogic’s Dynamics 365 Professional Services aid businesses in getting a single 360-degree view of their prospects. Accelerate sales by automating the whole process from inquiry to client onboarding, going beyond pre-built functionality based on your own tailored functions and features.

Dynamic 365 Customer Service

Microsoft Dynamics 365 Customer Service supports enterprises by streamlining service operations, increasing service agent efficiency, and building customer loyalty. Inogic’s extended CRM capabilities, such as plug-ins, bespoke business apps, scripts, and more aid in customizing Dynamic 365 Customer Service for enterprises to improve their customer service and retain more customers.

Dynamic 365 Field Service

Field Service 365 in Dynamic CRM enables uninterrupted field services and customer relationship management by analysing obtained data insights. Businesses can utilize Inogic for Dynamics 365 field service outsourcing to optimize and automate daily manual activities such as tracking, managing, and maintaining work orders, allotted resources, schedules, and ad hoc requirements in order to optimize resources, boost productivity, and successfully engage customers.

Power Apps

Power Apps is an excellent platform for automating internal processes. The Inogic team understands the app’s needs to design, construct, and execute the app while also allowing for seamless integration with existing platforms, processes, and apps.

Power Pages

Power Pages is a low-code/no-code portal solution that allows organizations to share information with their customers/partners without giving them actual access to CRM. Inogic Power Platform Techno-functional consultants build portals from the ground up, modify existing ones, migrate web-based portals to Power Apps Portals, and more to automate processes for people outside of an organization in order to simplify and shorten the time required to complete routine tasks.

Power Automate

Power Automate enables the creation of automated workflows between applications and services to synchronize or manipulate data, send notifications, and do other operations. Inogic power platform professional services assist in the identification of processes to be automated, flows to be followed, and background processes to save time and money while lowering the risk of human error, through automation.

Power BI

Businesses can make intelligent decisions to increase sales and profitability based on data-driven insights from the combined capabilities of Microsoft Power BI and Microsoft Dynamics 365 CRM. Inogic Services aid organizations by developing complex Power BI reports and dashboards that allow for data analysis and presentation.

Power Virtual Agents

Power Virtual Agents let users create intensely powerful chatbots that can answer questions posed by your customers, other employees, or visitors to your website or service. Inogic helps in creating powerful AI-powered chatbots for a range of requests—from providing simple answers to common questions to resolving issues requiring detailed and quick communication, thus capturing missed opportunities and improving customer satisfaction.

AI Builder

AI Builder enables you to use artificial intelligence (AI) to optimize your business processes. With Inogic’s bespoke AI models within Power Automate, Inogic can create custom models matched to your needs or choose a prebuilt model that is ready to use for many typical business scenarios.

Inogic Professional Services division is intended to enable everyone in your business to deliver to their full capacity. By choosing Inogic, a Microsoft Certified Gold Partner based out of India, you can accomplish automation with Dynamics 365 deployment through proper planning and competent execution. We are widely recognized for providing best-in-class Microsoft CRM solutions when it comes to Microsoft Dynamics 365 / Power Platform customization and configuration. Inogic’s industry expertise can assist you in accelerating process flow, and improving efficiency, and seamlessness across your industrial environment. Our extensive CRM expertise of more than 15 years has enabled us to give exceptional Microsoft Dynamics 365 services with genuine customer satisfaction and superior quality, allowing you to elevate your professional service practices and begin optimizing potential growth and scalability.

We’ll see you in our next blog, Part 2 of a two-part series, where we’ll talk about how Inogic provides Dynamics CRM Outsourcing Services on Dynamics 365 CRM and Power Platforms. Email us at crm@inogic.com or visit our website for FREE Quote.

Please visit the Source and support them

The post Techno-Functional Consulting for Microsoft Dynamics 365 CRM and Power Platform by Inogic appeared first on Microsoft Dynamics 365 Blog.

In this blog, we will see how to enable Administration Mode from Power Platform Admin Center. Enabling the Administration Mode comes in handy while performing operational changes to the environment like copying a sandbox instance to the production. Previously, this setting was available from the Office 365 portal for sandbox instances. For more details, you can refer to this blog.

Administration Mode can be enabled for Sandbox, Production, and Trial (Subscription-based) instances. So once enabled, only the users with the security role of System Administrator and System Customizer can access the environment. Enabling the Administration Mode ensures that neither non-administrators nor administrators affect each other’s work.

Let’s see how to configure ‘Administration Mode’:

1. Navigate to Power Platform Admin Center Login with Environment Admin or System Administrator -> Navigate to Environment from the left-side menu.

2. Select the Environment and Click on Open.

3. In Details, select Edit.

4. Enable the Administration Mode.

5. Post enabling the Administration mode, you will get the option to disable or enable the Background Operation. By default, this option is enabled.

If you disable the Background Operation, it will disable all asynchronous operations like workflow, and synchronization with Exchange.

6. Now the Custom Message field is no more editable as it is being removed -> Click on Save.
7. After saving, the environment gets updated.

Once it is completed, you can see a notification on the Environment page stating that ‘This environment is currently in administration mode, so only admins can sign in to it. You can turn off administration mode in settings’.

Now, only users with System Administrator or System Customizer security role can successfully access the environment.

Whereas, other end users i.e. non-admin users will not be able to access the environment.

Conclusion:

In this way, administrators can manage and maintain the environment by setting it in the ‘Administration Mode’ from Power Platform Admin Center.

Please visit the Source and support them

The post Enable Administration Mode from Power Platform Admin Center appeared first on Microsoft Dynamics 365 Blog.

In our recent project, we created a PCF Control in which we designed a date-time control. In the same control, we had a requirement to format the input date value to the given Date/Time field behavior in the date/time field of Dynamics 365 CRM. In Dynamics 365 CRM, date/time field have three types of behavior such as User Local, Date Only, Time-Zone Independent as shown in the below screenshot:

To achieve this, we have used the formatTime method of formatting API in Power Apps. With this method, you can format the date/time values in dateTime field behavior.

Please find below the code to format the input date/time values in PCF Control:

//Function that return result in datetime format from input date value formatToTime (context: ComponentFramework.Context<IInputs>, inputDateValue:any) { return context.formatting.formatTime(inputDateValue, 0); } //Function that return result in datetime format from input date value formatToTime (context: ComponentFramework.Context<IInputs>, inputDateValue:any){ return context.formatting.formatTime(inputDateValue, 1); }

After running the debugger, the result of formatting input date/time values to dateTime format will be as below:

Conclusion

With the help of Formatting API in Power Apps, we can easily format the input date values to the dateTime behavior format.

Go to Source and hit them a thumps up

The post Format date-time value using Formatting API in PCF Control appeared first on Microsoft Dynamics 365 Blog.

The ability to search a record by scanning its barcode is an intuitive and useful feature making the searching process quite easier. In our previous blog you saw adding of the Barcode field in the Case form. By adding this you can scan any Barcode and unique value of that Barcode will get updated in the barcode field on Case form.

We can add Barcode field in any of the forms in CRM. Also, we can search the barcode globally.

Global search will help the users to search the records quickly in the CRM.

Through Global search we can simply scan the Barcode using the Scanner and after scanning the barcode, the user will able to see the records for which the barcode is scanned. After scanning the barcode in the search, we will be able to see the associated records because in the barcode field the unique code will get auto-populated when the user scans the barcode.

In this blog we will see how we can use Barcode Scanning to search for Products in Field Service Mobile App.

Below is the example of Global Search for Barcodes in the Field Service Mobile App.

• Add the Barcode field in the form as explained in the previous blog.
• Navigate to powerapps.com
• Navigate to tables.

• Select Products in the Table.

• Go to views under the Product table.

• Select the Quick Find All Products view.

• Click on ‘Edit find table columns’.

• Select the Barcode and click on Apply.

• The Barcode will get added in the ‘Find By’ section as shown below:

• Click on Save and Publish.

• Open the Field Service Mobile App in mobile.

• Click on Search icon.

• Click on Barcode icon to search the associated records with respective to the barcode.

• Scan the Barcode.

• Records associated with the scanned barcode will be searched and displayed.

Conclusion

As illustrated above, you can see how easy it is to use Barcode Scanning to search for Products in Field Service Mobile App.

Please visit the Source and support them

The post Global search and Barcode scanning in Field Service Mobile App appeared first on Microsoft Dynamics 365 Blog.

Recently, we came across a new method in PCF – retrieveRecordCommand. This method will help us to retrieve the related commands for specific record(s). It also gives the flexibility to retrieve only specific commands that the user wants to see.

So, let’s see a scenario in which this method would come handy. Let’s say we want to show a PCF Dataset Component in a sub grid without the OOB Command Bar, which is very much possible. But what if we also want to execute some of the OOB commands in some events. This is where the retrieveRecordCommand method would save the day.

Using this method, you can retrieve the commands and once you have access to those commands, you can even trigger them by using the execute method.

Given below are the few parameters for the retrieveRecordCommand method.

Now let’s see how we can accomplish the above scenario.

Working:

We have a sub grid of Contacts on Account, where we have configured our Detail List Fluent UI component. Above the list, we have added a Command Bar fluent UI component i.e. a bunch of icon buttons. Here, we need two commands so we will add two options (refresh and download) in our command bar. You can add as many you may like.

By clicking these buttons, we will be executing the OOB commands as per the requirement.

Given below is the UpdateView function in index.ts. In this function, we are retrieving the commands that we need to execute later. The specificCommands is a string array including the commandButtonId of two OOB commands i.e. Export to Excel and Refresh Button.

We took all the record ids from context.parameters.sampleDataSet.sortedRecordIds so that the commands retrieved must be against these records as the name of the method retrieveRecordCommand says it all. This method retrieves the commands against the records that were passed in it.

After retrieving, the commands will render the DetailListGrid component.

public updateView(context: ComponentFramework.Context<IInputs>): void { let appProps: any = {}; //retrieve these commands let specificCommands: string[] = ["Mscrm.SubGrid.contact.ExportSelectedToExcel", "Mscrm.SubGrid.contact.RefreshButton"]; try { if (!context.parameters.sampleDataSet.loading) { // columns for detail list grid let columnsOnView = context.parameters.sampleDataSet.columns; //records ids in a string array let recordIds: string[] = context.parameters.sampleDataSet.sortedRecordIds; //retrieve specific commands for all the records context.parameters.sampleDataSet.retrieveRecordCommand(recordIds, specificCommands).then((commands: any) => { //get records for detail list grid let pageRows = this.getAllPageRecords(columnsOnView, context.parameters.sampleDataSet); //data sending to DetailsListGrid component appProps = { columnsOnView, pageRows, context, commands }; //rendering DetailsListGrid component ReactDOM.render(React.createElement(DetailsListGrid, appProps), this._container); }).catch((error: any) => { console.log(error); }); } } catch (error) { console.log("updateView " + error); } } 

In DetailListGrid component, we have a CommandBar and DetailList component. Below is the render method where we have called both the components.

Here, in <CommandBar /> Fluent UI component we have items i.e. left-side command bar and farItems i.e. right-side command bar. Since we want our buttons to be appear on right side, we added the items in the farItems.

public render = () => { const farItems = this.getFarItems(); const items = this.props.pageRows; this._columns = this.mapCRMColumnsToDetailsListColmns(this._columnsOnView); return ( <Fabric> <CommandBar items={[]} farItems={farItems} ariaLabel="Use left and right arrow keys to navigate between commands" /> <MarqueeSelection selection={this._selection}> <DetailsList items={items} columns={this._columns} setKey="set" layoutMode={DetailsListLayoutMode.justified} selection={this._selection} selectionPreservedOnEmptyClick={true} ariaLabelForSelectionColumn="Toggle selection" ariaLabelForSelectAllCheckbox="Toggle selection for all items" checkButtonAriaLabel="Row checkbox" onItemInvoked={this._onItemInvoked} /> </MarqueeSelection> </Fabric> ); } 

getFarItems is the function from where we are getting our icon buttons. So, let’s check that as well. For only the icons to be visible and not the text, we set iconOnly property as true.

/** * Get Command Bar Items * @returns ICommandBarItemProps[] */ private getFarItems = (): ICommandBarItemProps[] => { let farItems: ICommandBarItemProps[] = []; try { farItems = [ { key: 'Refresh', text: 'Refresh', ariaLabel: 'Refresh', iconOnly: true, iconProps: { iconName: 'Refresh' }, onClick: () => { this.commandClick('Refresh') } }, { key: 'Download', text: 'Download', ariaLabel: 'Download', iconOnly: true, iconProps: { iconName: 'Download' }, onClick: () => { this.commandClick('Download') } } ] } catch (error) { console.log("getFarItems" + ' ' + error); } return farItems; }   Now, we have two icon buttons Refresh and Download. By clicking these buttons commandClick method will be called.   /** * check and execute the command * @param command */ private commandClick = (command: string) => { //get the commands from props let commands = this.props.commands; let specificCommand: any; try { switch (command) { //if refresh icon is clicked case 'Refresh': //find the refresh command from the commands array specificCommand = commands.find((command: any) => { return command.commandButtonId == "Mscrm.SubGrid.contact.RefreshButton" }); //execute the refresh command specificCommand.execute(); break; //if download icon is clicked case 'Download': //find the download command from the commands array specificCommand = commands.find((command: any) => { return command.commandButtonId == "Mscrm.SubGrid.contact.ExportSelectedToExcel" }); //execute the download command specificCommand.execute(); break; } } catch (error) { console.log("commandClick" + ' ' + error); } } 

We have wrote a switch case and find method to identify the command. If you want to add more commands you can add them in the commands array while retrieving this switch case.

In this function, we checked which icon button was clicked, found the command related to it, and executed the same.

After clicking on the download button, export to excel command will run and the excel file will be downloaded.

Conclusion:

Thus, we saw how we can retrieve the OOB commands and execute them in PCF Dataset Component.

Go to Source and hit them a thumps up

The post Execute Commands Programmatically in PCF Dataset Component appeared first on Microsoft Dynamics 365 Blog.

As new features and functionalities are being introduced in PowerApps Component Framework, we have observed many new methods in the PCF Dataset Component. In this blog, we will discuss about the new entity record methods which are going to replace the WebApi update methods and custom requests to update the records in the dataset component.

Now, let’s understand these methods with the help of a scenario.

Scenario:

Let’s consider a subgrid of employees where we have configured a Detail List Fluent UI component. In addition, we have a two-option field named as Email Verified (Yes/No), on which we have rendered the Toggle component of Fluent UI.

Here, our goal is to update the value of the Email Verified as well as the Registration Status fields on change of the Toggle on Email Verified. Based on the value of the toggle we shall not only update the value of Email Verified to Yes/No in the background but also set the value of the Registration Status to Registered when the toggle is Yes or Unregistered when the toggle is No.

As shown in the above image, if we click on the toggle to change, it will trigger a method, where we would use the setValue method to change the value of the above mentioned fields and after that we will need to make use of the save method to save the changes.

The save method is an asynchronous method. It saves the value of only those fields whose values were changed by the setValue method and not all the columns in the table.

In addition, after the save method is called the dataset does not update automatically. To get the latest dataset in your control, you will need to call the updateView again and for this you can use requestRender or refresh method. The best place to call the updateView will be in the success callback of save method.

Code:                                                                                                                                                            

/** * On Change of Email Verified field toggle * Update the email verified and registration status fields of the repsective record. * @param event - mouse event * @param checked - boolean value of the checkbox */ private onChangeOfToggle = async (event: any, checked?: boolean) => { //local variables let guid: string = ""; let record: any = null; try { //get the guid of the record whose toggle is changed guid = event.target.id != "" ? event.target.id : event.target.parentElement != null && event.target.parentElement.id != "" ? event.target.parentElement.id : ""; //get the record from dataset record = this.props.pcfContext.parameters.sampleDataSet.records[guid]; //setting the value of email verified field - record.setValue(columnName, value); record.setValue("new_emailverified", checked); //setting the value of Registration Status field based on checked value record.setValue("new_registrationstatus", checked ? "Registered" : "Unregistered"); //saving the record with save method await record.save(); //refreshing the dataset this.props.pcfContext.parameters.sampleDataSet.refresh(); //testing this.test(this.props.pcfContext, guid); } catch (error) { console.log("onChangeOfToggle " + error); } }

Now let us see the functionality explained above in action. When I change the toggle of Maria Campbell record, the Registration Status get changed from Unregistered to Registered as can be seen in the below screenshot:

Now, if you open the record and check, you will find the updated values for both the fields on the form as shown below:

Conclusion:

Thus, we have learned how to utilize the new setValue and save methods by updating different fields.

Go to Source and hit them a thumps up

The post How to use the SetValue and Save Methods in PCF Dataset Component appeared first on Microsoft Dynamics 365 Blog.

With Power Automate FLOW, we can execute a huge number of operations by connecting various systems. Now, we are talking about the Dynamics 365 CRM where we can execute the Actions of Dynamics 365 CRM. Here, we know that with the “Perform an unbound/bound” action step we can execute the CRM actions. So, we are trying to execute one of the CRM actions that are “WIN/LOSE OPPORTUNITY” but this action is not that simple as compared to other actions.

Here, you can see we have “WinOpportunity” action is available in the “Perform an unbound action” but this action is not working as per our expectation and we are getting below error.

So, to execute the “WIN Opportunity” action, we found an alternate solution. Let’s discuss the same to WIN an opportunity using Power Automate FLOW.

Solution:

To WIN opportunity using Power Automate FLOW, follow the steps given below:

1. Basically, we need to specify the action name inside the “Perform an unbound action”. No need to use its in-build option to select “WIN Opportunity” as we tried above.
2. So, for this you need to store the Action name in one Variable as you can see in the below screenshot:

3. After storing the “WinOpportunity” action name, you need to map this variable to ‘Perform an unbound action” step where your “WinOpportunity” action will be executed.

Note: Here we must store the Action name inside the Variable. We cannot directly write “WinOpportunity” name inside the “Perform an unbound action” step.

4. Map ‘actionName’ variable in Action Name.
5. Set the parameters of the Action like Opportunity ID as shown below:

6. After setting the action parameters, the steps will look as below:

7. With this above step, we can execute the WinOpportunity action easily.

Similarly, we can execute the Lose Opportunity as shown below:

In “Status” you can pass the 4 (Canceled) or 5 (Out-Sold) according to your requirement.

So using this you can close the opportunity as Lost.

Conclusion:

In this way, by using Power Automate FLOW we can WIN/LOSE Opportunity in Dynamics 365 CRM/CE.

Please Follow the Source

The post How to WIN/LOSE Dynamics 365 CRM Opportunity through Power Automate FLOW appeared first on Microsoft Dynamics 365 Blog.