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.