Retrieve Quick View Value using JavaScript in Dataverse Environment

 Implementation Steps:

 

What is Mean by Quick View?

 

If we want to Populate data from One Entity to Another Entity based on Lookup then we can easily create Quick View Form to display the same.

 

Navigate to Forms --> Open main form --> Select Quick View Component and select respective entity and its Quick Form 

 

Javascript

 

Quick View Form Name : QuickViewContact

 

 

 

 

function getQuickViewForm(executionContext)
{
// get form Context
   var formContext = executionContext.getFormContext();
// get Quick View Contact
   var quickViewControl = formContext.ui.quickForms.get("quickviewcontact");
// get First name
   var firstNameControl = quickViewControl.getControl("firstname");
// Show Alert Dialog from FirstName
   Xrm.Utility.alertDialog(firstNameControl.getAttribute().getValue());
}

 

 

 

Timer Control in PowerApps

 Introduction: 

In this Blog we will see how to Create and Use PowerApps Timer Control in Dataverse Environment.

 Implementation Steps:

 

1. Navigate to https://make.powerapps.com

 

2. Create a new Solution

 

3. Add an Existing Entity or Add New Entity 

 

4. Create New Field

         --> Timer End date (Date and Time)

         --> Timer Start date ( Date and Time)

         --> Status Field with (In-Progress, Pending, Completed) (Choice)

 

 

5. Add the Created Fields in the Form

 

 

6. Now Navigate below Steps

• Navigate to https://make.powerapps.com
• Click Gear Icon at the Top  --> Select Advance Settings
• Select Cuztomization --> Click Customize the system
• Expand Entities --> Expand the Table where you have created the fields
• Click Forms --> Open Main Form
• Click Insert at the Top then Select TIMER

 

 

7. Enter the Name and Label

 

• Failure Time Field --> When Timer Should be Failed
• Success Condition --> When Timer Need to be Success
• Failure Condition --> When Timer Need to be Failed
• Warning Condition --> When Timer Need to be Warning
• Cancel Condition --> When Timer Need to be Cancelled
• Pause Condition --> When Timer Need to be Paused

Based on the Attached Imaged I have used my END Date and TIMER STATUS

 

if Status = Pending  (TIMER SHOULD BE : Paused)

 

 

if Status = In-Progress (TIMER SHOULD BE : Warning)

 

 

 

 if Status = Completed (TIMER SHOULD BE : Success)

 

 

 

That's it 

 

Please find my video for Step by Step Process

 

Retrieve Quick View Value using JavaScript in Dataverse Environment

Introduction:

In this Blog we will see how to get Values from Quick View Form

Implementation Steps:

 

What is Mean by Quick View?

 

If we want to Populate data from One Entity to Another Entity based on Lookup then we can easily create Quick View Form to display the same.

 

Navigate to Forms --> Open main form --> Select Quick View Component and select respective entity and its Quick Form 

 

Javascript:

 

Quick View Form Name : QuickViewContact

 

 

function getQuickViewForm(executionContext)
{
// get form Context
   var formContext = executionContext.getFormContext();
// get Quick View Contact
   var quickViewControl = formContext.ui.quickForms.get("quickviewcontact");
// get First name
   var firstNameControl = quickViewControl.getControl("firstname");
// Show Alert Dialog from FirstName
   Xrm.Utility.alertDialog(firstNameControl.getAttribute().getValue());
}

 

 

That's it 

How to get Error Message from Try Block using Microsoft Flow

Introduction 

In this blog we will see how to get the Error Message from TRY in Catch block using Microsoft Flow

Implementation Steps:

1. Navigate to https://flow.microsoft.com

2. Create a new Flow

3. If we follow existing Blog then we can use Try Catch block easily but we cannot get the error message from TRY block to Catch Block

Lets see how to Achieve that

in the Catch block just write result('TRYBLOCKNAME')

In my case it is result('Try')

Thats it :)

Now when an error Message occurs in Try block it will automatically catch the Error Message in Catch Block.

Hide Flow Button in Microsoft Dataverse Environment

 Implementation Steps:

 

After Creating Dataverse environment, in all the OOB or Custom Entities you will see a Button called FLOW like below screenshot

 

 

Lets see how to Hide it.

 

1. Navigate to https://make.powerapps.com

 

2. Click Gear Icon at the Top

 

3. Select Advance settings

 

4. Now Navigate to Administration then Click System Settings

 

 

5. Turn Off

 

 

Make sure once you turned on you cannot turn it off

 

 

If you want to hide it, you need to hide using Ribbon work bench

How to Create Quick View in Dataverse or MSCRM Environment

Introduction:

In this Blog we will see how to create Quick View in Dataverse/ MSRM Environment.

Scinario:

I have an Account and Opportunity Entity Available, in Opportunity Entity I have Account lookup Available, I need to display Account related fields in Opportunity form without any custom code.

Lets see how we can achieve this Behavior.

Implementation Steps:

1. Navigate to https://make.powerapps.com

2. Click Dataverse

3. Open Account Table and Click Forms

4. Check Quick View Form Already Available

5. If Already Available we can use else we can create a new One.

6. For Creating a New One Click ADD FORM and Select Quick View Form

7. Once selected it will Open the Form --> Add all the Field Which needed in Quick View Form

8. Once Done Provide Name --> Save and then Publish.

9. Now Navigate to Tables Again and Open Related(in my case its Opportunity). Click on Form and Open Main Form or where you want to display Quick View Form

10. Click Components and Select Quick View Form

11. It will show a Popup Select the Lookup and then Select the Form Which we have created

12. Then Position it in Respective place in the Form.

That's it :)

Save Now and Publish.

Open the Opportunity Form Select the Account lookup you will be popped up with Account Related Information

Note:

It will be a Read only Field. 

Show Document Location Entity as a Tab in Dataverse or MSCRM

Introduction: 

In this Blog we will see how to display Document Location as a Default tab in Dataverse or MSCRM Envirnment.

Implementation Steps:

 

Consider if we have an account entity and we have configured SharePoint Integration for the Account. If we want to See the Document for Respective entity of Account, you need to Click Related to See the Document. 

 

 

If Customer Expects to see the Documents as a TAB there is no OOB functionality to implement the same, to achieve that we need to write a Simple JS to Show the same.

 

function onLoad(executionContext){
var formContext = executionContext.getFormContext();
var sharePointDocumentItem = formContext.ui.navigation.items.get("navSPDocuments");
sharePointDocumentItem.setFocus();
var DefaultTabToDisplay = formContext.ui.tabs.get("tabGeneral");
DefaultTabToDisplay.setFocus();
}

 

Call the above function in Onload of the Page(in my Case its Account Entity).

 

 

Note:

 

navSPDocuments -- > SharePoint Entity Document Location (Default For All)

tabGeneral --> Tab to Display Default 

 

That's it