D365 Project Service Automation Archives -

Tag Archives: D365 Project Service Automation

Fast tracking the sales process in Microsoft Dynamics 365 Project Service Automation with Power Apps and Power Automate flows

When it comes to creating a contract with Microsoft Dynamics 365 Project Service Automation (PSA), users often find that the path from opportunity to quote and contract is long, slow, and involves too many clicks. To make it more efficient and cut down on the number of clicks, we can combine the capabilities of Power Apps with Power Automate flows. People love tooling that helps take care of small steps automatically like creating a basic project-specific price list, the Quote line details, or milestones. Let’s understand what’s involved at each step to go from Opportunity to Quote to Contract and navigate the entire process more effectively. Navigating the process Step 1: Create the Opportunity by navigating to Opportunity Entity in Project Service App. Step 2: When saving the opportunity users run a Power Automate flow behind the scene that does the following things: 1. Create the Quote automatically based on the billing type. 2. Generate the Quote Line record. 3. Fills the project-specific Price List (developed in Power Apps). This is now very easy to edit since the interface becomes more user-friendly and it directly updates the Roles Prices in the Pricelist. This, too, is a lengthy process with the out of the box capabilities of PSA. 4. Generate the Quote Line Detail, with one line developed in Power Apps. The details will include: a) Developer b) Quantity set as one hour c) Choose the rate from the default pricelist on the opportunity. Step 3: Now the Salesperson opens the Quote Line Details to add more lines in case needed. For this, I prefer adding one line to each role and adjusting the quantities appropriately to reach the quote amount. Step 4: After the Quote is ready and the negotiations are done with the client, we proceed to win the Quote, which does the following: Marks the Quote as won Creates the contract automatically with all the information in the quote (using an OOB feature) Automatically marks the related Opportunity Won. This is done via a flow which looks for the Opportunity from where the Quote was created and marks it as won. This is typically a manual process in PSA, but using Power Automate, users can also first navigate to the opportunity and mark it as won. Conclusion This process demonstrates the power of Power Automate flows and how much time they can save for a salesperson. The regular process takes lots of clicks and entries to be done right and hence is time consuming when done manually. Power Apps also helps you improve the UI and enrich the look and feel of the app. It also helps in reducing the navigation between entities and thus saves a lot of time.

Overbooking Bookable Resources in D365 PSA v3

Mircosoft D365 Project Service Automation is a product that unites technology, processes, and people together in streams such as sales, billing, resourcing and delivery in a company. Thus, a business can scale up high when they use this particular software. They can complete the project on time and within the budget as a result of using this product from Microsoft.  Businesses can accelerate the maturity of their professional services when they use this software. Managing the project becomes easy for the management team and the project managers. Learning and using software is also pretty easy. It does not take a lot of time to master this product.  Here are some details of how this software will help your company: While booking resources, you often don’t pay attention to how much capacity the resource has. Or rather, you are aware, but you want to book the resource anyway (only to change later on, which I don’t recommend.) In that case, if you are trying to overbook a resource out of their capacity, you are treated with this message below – Why this occurs? This is because of the Work Hours defined for the Resource. Rather, what Work Hour Template is assigned to that resource. Now, let’s say, you are trying to book someone for 8 hours on top of their already booked 2 hours If you switch to the Hours view, you’ll see the availability marked by white cells. Grey meaning, unavailable. Remember, this is even said in the error message when you tried to click Book. Alternative Of course you can do this, but you should have a very strong reason to overbook resources. 🙂 Switch to Evenly Distribute Hours to allow the resource to be booked on top of the existing one. And this should be fine, but it will appear in red indicating that the resource is overbooked. Say, 10 hours (on top of already booked 2 hours) – exceeding the 9 hours total limit. Suggested You should rather Propose Book the resource, this way, the booking will exist and won’t bloat the schedule board. And then, you can decide later to do something with it. Front Load – Proposed Now with combination of Front-Load and Proposed, you should be able to Book for only the remaining capacity Evenly Distributed – Proposed With Evenly Distributed Proposed, you should be able to exceed the capacity and even Propose for the full time you want.   Hope this quick tip helps! 🙂  

PSA Quick Tip: How to Give Team Members Access to Only do Time Entries and Expense Entries and not Expose Other Entities in PSA v3.X

Dynamics 365 Project Service Automation helps companies to have control over the projects that they undertake. It is the main reason why a lot of companies love this particular ERP solution. Companies can complete the project within the timeframe and the budget that is allocated. Estimating the project budget and planning resources becomes a lot easy. Communication between employees in the company improves substantially. Microsoft Dynamics 365 for Project Service Automation equips the project managers with the essential tools to make them efficient. It helps companies to become organized and to become successful. Here are some quick tips on how you can give your colleagues access that is necessary to do expense and time entries without exposing them to other available entities on the system. Dynamics 365 Project Service Automation is a software application that companies need to buy and use if they want to have full control of a project. Organizations can use this application to manage, track, and deliver project-based services on time. Creating work schedules and quotations utilizing this system is secure. You can manage and assign resources with ease when you use this software. Mastering how this system works is quite essential if you desire that your projects become successful. You might encounter so many unique problems when you are using this particular system. Here are some probable solutions that will help you to solve these problems. Problem Definition: We sometimes have a few team members who only need to do the time entries and expense entries. They do not need any exposure to other entities. How do we make it possible via the OOB (Out of the box) security roles in PSA V3.X. Solution: From the security–>Users–> select the user–>Manage Role and Only keep “Project Resource” Role. 2. Go to Security–>Security Roles–>Open the security Role “Project Resource” –> change the following 2 parameters read/write access as shown below in the image. 3. Log off and log in again and you are set 🙂

First Canvas Power App: Learn Few Easy and Important Commands

These days there are so many companies that are developing software applications to help businesses manage the projects. But, nothing comes close to dynamics 365 project service automation. It is unique and is one software that every business should have if they want to manage projects and help them to become successful. Companies can track as well as manage projects well when they use this particular software.astering this software is essential if you want to use this application efficiently. PowerApps is one service that Microsoft offers, and developers can use it to build apps as per the requirement of the client. As my thoughts build to initiate writing this blog, similar was the feeling when I first thought about exploring Power Apps. The expression was, “What exactly is Power Apps?”. When the world is talking about it, it brings me more curiosity to understand what is so powerful about it. Let’s first commence with understanding what exactly is Power Apps: PowerApps is an initiative by Microsoft that allows developers and nontechnical users to build mobile applications from selectable templates. The objective of PowerApps is to enable business users to build new capabilities via apps, without requiring that they have code expertise. Types of Power Apps: Model driven apps: These types of apps directly publish the entity on the mobile/ tablet. These apps can be used from Microsoft Dynamics 365 App from mobile. They are very easy to make and can be ready within 15mins of time. Canvas apps: These apps are blank canvas given to the developers with a free hand to design the app in the way they want. In this blog we shall focus more on how to make a Canvas app. Follow the steps below to make a PowerApps. Step 1: Login to www.portal.office.com Step 2: Click on PowerApps icon as shown in the image below: This will open a new browser tab where we need to select what kind of app do we need to make. Step 3: Click on Canvas app from blank, which opens a pop up. Please name your app and select whether the app is for Phone or for Tablet as shown below and click on Create button. This opens the Canvas app editor as shown below: To take this blog forward, I will use an app that is created by me and explain a few commands used by me and how was the design done in that app. The app captures the Grievances of people in office. There are 5 screens created by me and they are: list_Grievances Screen: This list all the grievances in the system. 2. frm_GrievanceRecord Screen: This opens a grievance record. 3. Frm_NewGrievance Screen: This screen is used to capture a new grievance. 4. Frm_CameraScreen : This is used to capture the image of the grievance using camera control. 5. SuccessScrn: This is used to display the success on the screen. Technical dive Let’s take a dive in each screen and get into understanding of functionalities developed on each screen: List_grievances: a. New Grievance button: This button will navigate to a frm_NewGrievance Record to capture new grievance from the employee. The code written behind that is:………………………………………………………………………………………………………………Navigate(frm_NewGrievance,ScreenTransition.Fade );   …………………………………………………………………………………………………………………….b. To display the list of Grievance I have inserted a List Screen as shown in the image below: c. To display the list of Grievance, we need to add a Data Source. How to add a data source is shown below: There are approximately more than 250 Data sources to which Power apps can connect. Select the data source you wish to connect. In my case, I will connect to Dynamics 365 Data Source. It will ask you to choose your entity and then you can click on connect. Your Data Source “Grievances” will start appearing in Items drop down of Property Window. Post that we can align the attributes that we need to see on the list view: To Display Employee Full Name, below is the code that I wrote: ………………………………………………………………….. ThisItem.’Employee Full Name’ ………………………………………………………………… To get the department value, which is a lookup to another entity below is the code that was written: …………………………………………………………………. LookUp(Departments,new_departmentid=ThisItem.Department, new_name) …………………………………………………………………. To display the image from the SharePoint Library, below is the code: LookUp(GrievanceLibrary, Title = TitleGrievance.Text, Image)   Where GrievanceLibrary is the Sharepoint Datasource added in Powerapp and Title and image are the fields created in SharePoint.   To open the Grievance record on frm_Grievance Record, write the below code: Navigate(frm_GrievanceRecord,ScreenTransition.Fade,glryGrievances.Selected)   frm_NewGrievanceRecord: To store the new grievance record, we used the Form Screen. On the update button, write the below code: Patch(     Grievances,     Defaults(Grievances),     {         new_employeefullname: DataCardValue3.Text,         new_description: DataCardValue15.Text,         _new_departmentl_value: DataCardValue10.Selected.new_departmentid,         _new_grievancetypel_value: DataCardValue6.Selected.new_grievancetypeid,         new_signature: PenInput4.Image     } ); Patch(     GrievanceLibrary,     Defaults(GrievanceLibrary),     {         Title: DataCardValue3.Text,         Image: First(Collection1).Url     } ); UpdateContext({resettext: !resettext}); UpdateContext({resetcombobox: !resetcombobox}); Navigate(SuccessScrn,ScreenTransition.Fade); frm_CameraScreen Insert a Camera Media Control on the form as shown in the below screen shot. Insert an image control on the form below the Camera Media control. Capture button code: ClearCollect(Collection1, Camera1.Photo) Collection 1 s described above is the SharePoint collection object which needs to be cleared and then referred with the new Photo from the Camera Control, which in our case is Camera1. Confirm button code: Confirm Button will only Navigate it to New Grievance form and the code is ass per below: Navigate(frm_NewGrievance)  To summarise: We learned how to create a Canvas Power app. Different controls that can be used. How to store image on Sharepoint in a Power app. Again I am sharing the code for storing the image on Sharepoint herewith: Patch(     GrievanceLibrary,     Defaults(GrievanceLibrary),     {         Title: DataCardValue3.Text,         Image: First(Collection1).Url     } ); To explain the above code, GrievanceLibrary is the SharePoint site of which Data Source is added. Title: This is a field in the Sharepoint library that will store the name of the Grievance. The data type in Sharepoint for Title is Single line Text Image: This will store … Continue reading First Canvas Power App: Learn Few Easy and Important Commands

SEARCH :

FOLLOW CLOUDFRONTS BLOG :

FOLLOW CLOUDFRONTS BLOG :


Secured By miniOrange