Posts

Showing posts from August, 2019

Update Business Process Flow Using Flow

Image
When working through App In A Day Workshop I wanted to improve the Approval flow to move the Business Process Flow (BPF) Stage forward if the Device Order was Approved.  I have utilized plugins and workflow previously to accomplish this type of action but never with Flow.  After doing a quick search i found an article from Elaiza Benitez (Automatically update the stage of a Business Process Flow with Flow 2.0), make sure to check it out it's great.  My post here utilizes the techniques Elaiza provided but applies it to the Device Approval Request Flow as part of the App In A Day workshop.

Below if the final Device Approval Request.  The parts I added to the BPF are outlined in Red.

The first thing we need to do is get the Device Procurement Process record for the Device Order that applies to the BPF we build in the workshop.
Next we need to parse the returned record using the Parse JSON action.  In order to get the schema for this action just run the Flow with the previous action …

Get Dynamics/CDS Base URL in Flow To Generate Links To Record

Image
When sending emails or approvals in flow it can be helpful to also include a link to the record which is being referenced.  In order to send those links though we need the environment URL of the Dynamics/CDS environment.  This article shows an example of how to get the base URL for the environment and how to build a link based upon it. 

This will be demonstrated within a Flow created for the App In A Day Workshop. In this Flow we are attempting to get an approval when a Device Order entity record is created from our Canvas App.  The Approval step allows us to include a link to the item and we will also be sending out emails to the requester based upon the Approval outcome which will include the link.

The first Action we need to add to our existing workflow is the CDS Get record step.  Why do we need this step?  Well unfortunately the Output that is provided from the Flow Trigger of when a record is created does not include the URL to the record.  Instead we need also include the Get r…

PowerApps Naming Conventions and Coding Standards

When building canvas apps the naming conventions used by the objects can be very confusing once you have added a few screens.  It is important to make sure you rename your components while working to allow for better readability and supportability of your application.  Below are some common naming conventions which are available within the PowerApps canvas app coding standards and guidelines whitepaper.

Control nameAbbreviationbutton btncamera control  camcanvas  cancard  crd collection  colcombo box  cmbdates  dtedrop down  drpform  frmgallery  galgroup  grpheader page shape  hdrhtml text  htmicon  icoimage  imglabel  lblpage section shape  secshapes (rectangle, circle, and so on)  shptable data  tbltext input  txttimer  tim