Strange Popup in Power Apps Confirm(): What’s Happening?

 Introduction:

In this blog we will see how to show New Confirm Pop up in canvas PowerApps

Implementation Steps:

• Navigate to https://make.powerapps.com
  
  
• Create a new App
  
  
• Change your App to New version
  
  
• Write Below Code
  
  
  • Confirm("Confirm Button Popup");
    
    
    • 
      
• You will see browser PopUp
  
  
• But this is not an Actual Canvas App Popup, Lets see how we can get new Canvas PowerApps Confirm()
  
  
  • Click Settings
  • Select Updates
  • Look for Modern controls and themes
    • Toggle it ON
  • Click Close
    
    
    
• Now Click the same button
  
  
• Now you will get the Confirm() canvas Pop Up
  
  
  
  
  

Conclusion:

By following above steps we can get rid of Browser Popup and get the new Canvas App popup.

Understanding the Confirm Function in Canvas Power Apps

 Introduction:

In this blog we will see how Confirm Function works in Canvas Power Apps.

Implementation Steps:

• Open https://make.powerapps.com
  
  
  
  
• Select Apps and Click New App and Select Start with a Page design
  
  
• Select Blank Canvas App and Click Create
  
  
  
  
• Once Page Opened, Verify the below PreRequisites
  
  
• Click Settings, select Support and make sure it is in Latest Version
  
  
  
  
  
• Once Selected Click Reload + apply version
  
  
• Save the App with Name
  
  
  
  
• Now Click Settings and Enable Modern Controls and themes
  
  
• Once App Loaded add a button 
  
  
• On Select of Button Write below Code
  
  
  • Confirm("Confirm Button Popup")
    
    
    
• Now Add below Code
  
  • Set(getSelectedOption,Confirm("Confirm Button Popup"));
    
    
• Add a label to form and provide Text as "getSelectedOption"
  
  
  • Now when user selects Confirm you will get response as True 
    
  • If User selects cancel you will get response as False
    
    
• Now Try below code for Title and SubTitle
  
  • Set(getSelectedOption,Confirm("Confirm Button Popup",{Title:"Header Title",Subtitle:"Sub Title"}));
    
    
    
    
• Now Try below code to update Confirm and Cancel Button text
  
  • Set(getSelectedOption,Confirm("Confirm Button Popup",{Title:"Header Title",Subtitle:"Sub Title",ConfirmButton:"Ok",CancelButton:"Ignore"}));
    
    
    
    
• Now try below Code​​​​​​​
  
  • If(Confirm("Confirm Button Popup",{Title:"Header Title",Subtitle:"Sub Title",ConfirmButton:"Ok",CancelButton:"Ignore"}),Notify("Confirmed"),Notify("Cancelled"));
    
    Based on selection it will show Popup if you Click Ok it will Notify as Confirmed else Cancelled
    
    

​​​​​​​Conclusion:

Going further we don't want to spend much time in Creating Popup :) by having simple command we can achieve this.

How to disable Form JavaScript Using URL in Model Driven app and MSCRM

 Introduction :

How to disable Form JavaScript Using URL in Model Driven app and MSCRM .

Implementation Steps:

• Navigate to your Environment
  
  
• Open the Form which is Broken in my Case it is CONTACT FORM
  
  
  
• Copy the URL and Put it in NotePad
  
  
  
• Append the Below Script in the URL
  
  &flags=DisableFormLibraries=true
  
  
• Final Output Will be
  
  
  
  
• Verify Form Loads Successfully
  
  
• Now if the Form Loads successfully it confirms that the issue is with Code
  
  
• Now you can open the form and add Debugger and Start your testing.
  
  

Conclusion:

Based on above steps you can easily find the issue either it is from JavaScript or Form issue.

How do I patch a Currency field value from a Canvas Power App to Dataverse?

 Introduction:

In this blog, we will see how to patch a Currency field value from a Canvas PowerApps to Dataverse or MSCRM

Implementation Steps:

1. Navigate to https://make.powerapps.com
   
   
2. Click On Apps
   
   
3. Click New and select Start from Page Design
   
   
   
4. Click Create
   
   
5. Now once the page opened Add a Datasource called Accounts
   
   
   
   
6. Now Add a Gallery and Select Items as Accounts
   
   
   
   
   
7. Now Add a Form and Select Items as Accounts and Gallery.Selected as Account
   
   
   
   
   
   
   ​​​​​​​
   
8. Add a Column Annual Revenue ( in my case am using account table as my DS)
   
   
9. Add a Submit Button
   
   
10. On select of Submit button add below code
    
    

    Patch(Accounts,
    LookUp(Accounts,Account = Gallery1.Selected.Account),
    {'Annual Revenue':Value(DataCardValue1.Text)})

Descrption about Code:

1. Patch - Save the record to DB
2. Account - Table Name
3. Lookup Query - Retrieve the record to Update
4. Annual Revenue - Column Name
5. Value - As Annual revenue is my Column to update it will expect Number 

Conclusion :

Using above code we can patch Currency field to Dataverse or MSCRM.

How to disable recently used records in lookup fields in CRM and Dataverse?

 Introduction:

In this blog we will see how to disable recently used records lookup field values in MSCRM or Dataverse




In my case, I want to hide the “Recently Used” section in the Parent Account lookup so that only recently created records are shown. Let’s see how we can achieve this.

Implementation Steps:

1. Navigate to https://make.powerapps.com
   
   
2.  Select Tables
   
   
3.  Look for Account Tables 
   
   
   
4. In the Account Tables select the Forms
   
   
   
5. Open Account Form
   
   
   
6. Once the Form Opened select the field PARENT ACCOUNT
   
   
7. At the right side you can see an Option to Select "Disable most recently used items"
   
   
8. Click Save and Pubish
   
   
9. Now open the Model Driven App and click the same field you cannot see the Recent Accounts
   
   
   
   
   

Conclusion:

By following above steps we can easily disable most recent records from Lookup.

How to Show/Hide Particular Views based on Security Role ?

 Introduction:

In this Blog, we will see how to show or hide particular views based on Security Role

Implementation Steps:

• Navigate to https://make.powerapps.com
  
  
• Click Tables
  
  
• Select the Tables you want to Restrict the views based on Security Roles
  
  
  
  
  
• In my case am Taking Account Table into Consideration
  
  
• Click On Account
  
  
• Select Views
  
  
  
  
  
• Select the Views and Click View Settings
  
  
  
  
  
• You can see 2 Options
  • Everyone
  • Specific security roles
    
    
    
    
    
    
    
• Everyone
  
  • If you select Everyone all the users in the system can able to see the Views
    
    
• Specific security Roles
  
  • If you select this you need to select Particular Role to see the views
    
    
    
    
    
• Once done click Save and Publish
  
  
• Now Open your Model Driven App
  
  
• Open Account Entity You can see the Security Role Applied
  
  

Conclusion:

By following above steps we can easily show or hide views based on security role.

Create - Pre Operation - Dataverse Accelerator

 Introduction:

In this Blog, we will see how to Create Pre-Operation Plugin in Dataverse Accelerator

Validations:

In Contact if user selects Date of Birth greater than todays date throw Error

Implementation Steps:

• Navigate to https://make.powerapps.com
  
  
• Click Apps
  
  
• Open Dataverse Accelerator App
  
  
• Click New Button
  
  
  
  
• Select New Automated Plugins
  
  
• Input Display Name
  
  
• Select Table Name as Contact
  
  
• Select Run this Plugin as
  • Create Operation
    
    
• Input Below Expression
  
  • If(NewRecord.birthdate > Now(), Error("Birthday Cannot be future"))
    
    
• Then Select when this Plugin Should Trigger
  
  • In our case it is PRE-Operation
    
    
• Select Solution
  
  • ​​​​​​​Plugin to store
    
    
• ​​​​​​​
  
  
• Once you done this Click Save Button on the TOP
  
  
• Once Saved Navigate to Dataverse
  
  
• Click Contact
  
  
• Select New
  
  
• Fill all the Mandatory details
  
  
• Input Date Of Birth as Future date and Save
  
  • 

Conclusion:

This can be achieved in Plugins but in Dataverse/MSCRM we are having NoCode Low Code operation to achieve the same.

YouTube Link for your Reference : https://www.youtube.com/@rampprakash3991

How to Remove Unmanged layers in Microsoft Dynamics CRM/Dataverse

 Issues Faced :

When we need to create a new field or update a failed, we are having an different environment we are create in that and move as a Solution while moving that some times we cannot see the fields available in the destination environment.

How we can fix this ?

Implementation Steps:

1. Navigate to https://make.powerapps.com
2. Click Solutions
3. Create a new Solution or Open an existing solution which contains the table
4. If New or Old Solution
   1. Click Add Existing and Add Table
5. Now Expand Tables
6. Select Columns (Fields
7. Find the Problematic fields 
8. Check Solution Layers
   1. Click the Three dots next to the field Name and Choose Solution Layers
9. Delete Unmanaged Layer
   1. You will see all layers like Managed or Unmanaged
   2. If an Unmanaged Layer exists click Remove or Delete
   3. Now Confirm delete
10. That's it :)
    
    

Conclusion:

By following above steps we can easily removed unmanaged layer from the fields

How to Add Static Text to CRM or Dataverse Using HTML Web Resources

 Introduction:

In this Blog, we will see how to Add Static Text to CRM or Dataverse Using HTML Web Resources

 Implementation Steps : 

1.  Navigate to https://make.powerapps.com
    
2.  Click Solutions
    
3. Open the Solution or Create a New Solution
    
4. Click New --> Select Web Resource
    
5. Select Type as HTML
   

   

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
6. Input below Code

   <!DOCTYPE html>
   <html>
   <head>
       <meta charset="utf-8" />
       <title>Static Text</title>
       <style>
           body {
               font-family: "Segoe UI", Tahoma, Geneva, Verdana, sans-serif;
               font-size: 14px;
               color: #333;
               margin: 0;
               padding: 0;
               background-color: transparent;
           }
   
           .static-text {
               padding: 0;
               border: none;
               background: none;
           }
       </style>
   </head>
   <body>
       <div class="static-text">
           This is a static text.
       </div>
   </body>
   </html>
   

   
   
7.  Click Save and Publish
    
8. Open the form where you want to display this HTML
    
9. Like Account --> Information Form
    
10.  Once Form Opened Drag and Drop HTML
    
    
    
    
    
     
11.  Click Add
     
12. Now Save and Publish the Form
     

Conclusion:

This is one of the easiest way to add static text in MSCRM or Dataverse

​

Cancelled Appointments not synced in Outlook ?

 Introduction:

In this blog, we will see how to sync Cancelled Appointments in Outlook.

Implementation Steps:

• 1. Navigate to https://make.powerapps.com
  
  
• 2. Select Correct Environments
  
  
• 3. Select Gear Icon on the top and Click Advance Settings
  
  
• 4. Select Solutions and Import the attached Solution (OrganizationSettingsEditor_Managed.zip)
  
  
• 5. Once the Solution is Imported then Select Publish all customizations
  
  
• 6. Now search with "OrganizationSettingsEditor" and Open the Solution
  
  
• 7. Search for "SSSPropagateAppointmentCancellationsToExchange"
  
  
• 
  
  
• Click On EDIT
  
  
  
  
  
  
  
• Set the textbox to true (small case)
  
  
• Click Update
  
  
1. It will Prompt "Proceed with pushing a change into CRM?" Click OK
   
   

Conclusion:

That's it now Create an appointment and cancel it and it will get synced to Outlook.

How to View Flow Run History in Power Automate?

 Introduction:

In this blog, we will see how to View Flow Run History in Power Automate.

Implementation Steps:

1.  Navigate to https://admin.powerplatform.microsoft.com
   
   
2. Click Manage
   
   
3. Select Environments
   
   
   
4. Open the Environment where you want to change Run History of Power Automate
   
   
5. In my case it is Trail Environment
   
   
   
6.  Open the Environment
   
   
7. Click Settings and select features
   
   
   
8. Look for "Cloud flow run history in Dataverse"
   
   
   
   
9.  Update the History 
   1. Enabled - 28 days retention (default)
   2. Enabled - 14 days retention
   3. Enabled - 7 days retention
   4. Disabled
      
      
10. You can select the option how many days you want to be retained
    
    
11. Update the drop down and Select Save

Conclusion:

Based on above steps we can update the retention for Cloud flow run history in Dataverse.