Monday, June 7, 2021

Enhanced Email For Timeline in Dynamics 365


Microsoft is coming with yet another cool feature, Enhanced Email for Timeline for Dynamics 365 CE users. 

This enables users to create email, minimize and maximize window, while staying back on the main record. What an ease to Dynamics users.



Lets see how to enable this feature - 

Go to App Settings - Overview - Productivity Tools - Enhanced Email for Timeline  


Happy Learning, LET'S SHARE !

Saturday, June 5, 2021

Power Automate: Connection References missing in Dataverse Connectors [Reason?]


Problem Statement - While creating Power Automate we may face situation where connection reference for the Dataverse Connector missing and we could only see Connections. Moreover we dont see an option to add connection reference to the flow. 


As we know Connection References are preferred over Connections for smooth deployment so lets figure out what could be the possible cause. 

Lets create a sample cloud flow in our solution, here we can see Connection Reference available in the Dataverse connector.




Also, if we close the editor we can see Connection References box on the flow page. Yay !


Now, we have 2 components in the solution
i) Connection Reference
ii) Cloud Flow


Suppose, we need one more Cloud Flow with similar steps, as easy steps we go ahead and create a copy of the existing Power Automate.


Copy of Power Automate is added to My Flows, from where we add this to the Solution.


    To Add, we navigate to our Solution and add existing cloud flow to the solution.



Now Solution contains 3 components, an additional flow(copy) is also added, which we can go ahead and make changes.


All seems so quick and easy till now, but let's realize what changes are seen due to copy action. If we open the Flow(copy) we can't see Connection References it only has Connections.


Even if we open the Flow(copy) in editor we could only see Connections, Connection Reference is missing and we don't see any option to add Connection Reference to the flow thereafter.
This is weird !

Now if we deploy this flow to the target instance we will have to manually update the connection post deployment.

So as a practice, avoid creating copy of the Flows from within the solution as it ends up converting Connection Reference to Connections. 


Keep an eye on next article where we will see how can we fix the Flows to have Connection References instead of Connections.

Happy Learning, LET's SHARE !

Wednesday, May 26, 2021

Power Fx coming to Model-driven Power Apps and Dataverse

Microsoft is about to bring low code power for Model-driven Power Apps and Dataverse using Power Fx.

Some areas of innovation:
  • Model-driven commanding.  No longer do makers need to learn and write JavaScript to create their own commands!  The same Power Fx formulas used in canvas apps can be used to test and modify Dataverse data.
  • Dataverse calculated columns.  Use Power Fx formulas for calculated columns and rollups in Dataverse, a more modern and powerful alternative to existing facilities.

Monday, May 24, 2021

Step by Step Guide to create PCF Control


Objective - To Create Guid PCF Control

Pre-Requisites
 
  • Install Node Js - https://nodejs.org/en/
  • Install Power Apps CLI - http://download.microsoft.com/download/D/B/E/DBE69906-B4DA-471C-8960-092AB955C681/powerapps-cli-0.1.51.msi.
1. Create PCF Control
  • Create Project Folder
  • Navigate to Project Folder
           Command – cd <FolderPath>

  • Create Project Files in the Project Folder

    Once the Project Folder is created next step is to generate project files using the below command.

        Command: pac pcf init --namespace <your namespace> --name <your component name> --template <component type>

  • Verify Project Files in the Project Folder
  • Install Project NPM Dependencies
        Command – npm install
  • Update Property Node in Manifest File
  • Add CSS to the solution
  •  Update Logic in Init and UpdateView Method of Index.ts file
  • Build Control
          Command - npm run build

  • Run Control Locally
          Command - npm start
    
            Check Output -
    

  • Terminate Job - Press Control + C then followed by Y 

2. Package PCF Control Solution
    Once PCF control verified locally lets package into D365 CRM Solution. To package solution we would need ‘Developer Command Prompt for VS 2019’
  • Create Solution Folder
  • Create Solution Project

    Once Solution Folder is created, create Dataverse Project Files in solution folder.
          Command:  cd <D365SolutionFolder>

          Command: pac solution init --publisher-name <Your Publisher> --publisher-prefix<PublisherPrefix>

           Example - pac solution init --publisher-name Shreways --publisher-prefix shreways

  • Verify Solution Folder
          Dataverse Project Solution File Created Successfully

  • Update Dataverse Project File to get Managed/Unmanaged or both the solutions
  • Link PCF Control with Solution
    Command:
    pac solution add-reference --path "<PCFFolderPath>"
    Example - pac solution add-reference --path "C:\SAURABH\Shreways\PCF\GuidControl"
  • Archive Solution
          Command: msbuild /t:build /restore


           Once the comment runs successfully,verify the bin folder with CRM Solutions


3. Usage in D365
  • Import Solution in D365 CRM 
  • Create Field and Map the Guid Control

    Create Text Field on Entity and update field properties to bind "GuidControl" to the field.


          Save Changes and Publish.
  • View the GuidControl on Entity Form

    Account Id Field is populated with Guid of the account record.


We can embedd this PCF control to any entity where we need Guid to be mapped to a field.


Happy Learning, Lets SHARE !

Popular Posts