Create and edit tables using the table designer in Power Apps
By using the table designer in Power Apps Studio, you may create and modify Dataverse tables in canvas apps. Without leaving the program you’re using, you can manipulate the data in the table. Required permissions and limitations. Steps: Conclusion: We have the freedom to design data sources and record them in the Canvas app thanks to this capability. There is no need to travel to power apps to create a table. Thank you, Vijay for your valuable inputs to this blog!
Now Import Projects from Microsoft Project Desktop Client in Project Operations
Problem Definition: In contrast to Project Service Automation, where importing projects is made easy via a ribbon button, it was previously not possible for current Microsoft Project Desktop Client users to do so in D365 Project Operations. Project for the Web is supported by D365 Project Operations, although not all of Microsoft Project Desktop Client’s features are available. It was imperative to establish a connection between the two due to the system’s gap. Solution: Steps to import a file in Project Limitations: Project for the Web works well for the majority of projects, but it doesn’t totally replace Project desktop. The following features cannot be migrated or supported. Before you begin importing your project, make sure it doesn’t rely on these features. Cross-project dependencies, manual tasks, recurring tasks, subprojects, and even some types of selective constraint types like As late as possible, Start no later than, Finish no later than, etc. are a few characteristics. There are many such features which are not supported while importing. Refer given Microsoft link for more information: https://support.microsoft.com/en-us/office/move-your-project-from-project-desktop-to-project-for-the-web-143ab391-002e-451a-aedb-3b6fa1f6ab8b#bkmk_featuresthatdontmigrate Conclusion: Users will have the freedom to utilise any project planning tool of their choice, including Project Desktop Client and Project for the Web, thanks to this import feature. This functionality is a good complement to all the other functionalities in the product and will help D365 Project Operations meet more customer requests. Thank you, Sankalp for your valuable inputs.
Filter Grid data, and Save results as a View
Introduction: Views in model-driven apps specify the data that is tabulated and displayed on a grid page. Views that have been developed by an administrator, shared with others, and normally can’t be changed are called System Views. Dynamics 365 2022 release wave II includes a new functionality that provides the ability to save the filter conditions on a grid as a personal view as well as enables you to manage and share views. You can save time with this effective feature. Following types of views are available in model-driven apps: How to Filter grid data, and save results as a view? To select the filter condition, click on the Edit Filters To remove a condition, select More commands (…) next to the row, and then select Delete To add one or more conditions, select Add option The following options are available to add conditions in the filter editor To add a condition, select Add row, To select a value, click on the down arrow After editing the view filters, select Apply to see changes on the grid page How to Save edits as a new view? On the command bar, select More commands (⁝) > Create view > Save as new view Enter a new name for the view, and then select Save How to Manage and share personal views? To manage and share views, turn on the modern Advanced find options. Click on the Save button In the view selector, the Manage and share views option is available Select the Manage and share views option Select View commands (…) and then choose the Share option Select the user to share the view Set the permissions Select Share option Conclusion: This feature is helpful because it increases Productivity by preserving the quick find filter conditions as a personal view and it also optimizes time. References: – Filter grid data, save results as view | Microsoft Learn Thank you , Amisha for your valuable inputs
Project Operations vs Project Service Automation, A Seamless Comparison to Read
We know that PSA is now known as Project Operations. Well, it’s not just a name change but also some significant improvements that Microsoft has brought in. The following blog will take you through the differences between PSA and Project Operations. The upgrade from Project Service Automation to Project Operations is going to be delivered in three phases. Below are the major changes which will be seen after the upgrade is complete. In this phase, the dependency on WBS has been cut off for projects. With all the modifications from phase 1, we even have WBS that is a part of the project operations limits that are currently supported In addition to the enhancements from phase 2, WBS also includes support for the Project desktop client and extends beyond the present scope of Project Operations. Let’s delve deep in feature wise comparison between PSA and Project Operations. 1] Project Templates: They help you generate the WBS structure from an already pre-defined WBS structure in the form of a template. Project Service Automation: ✔️ Included You can create a project template as shown in below image in PSA: After saving this record, you can add the record while creating a new project as shown in the below image. You can also select ‘Is Template’ field to save the current project as a project template. Project Operations: Not included This feature is not included in Project Operations, but the same functionality can be done with the ribbon button on the Project form named ‘Copy Project’. With this all the task information and the project properties get copied in a new draft project. 2] Project work breakdown structure (WBS) integration with desktop client: A project management tool with automated scheduling, resource management, and built-in reporting is Microsoft Project Online desktop client. Project Service Automation: ✔️ Included This feature is very essential in PSA as with the capabilities of desktop client, Task management can be done efficiently. There is a ribbon button to integrate the system as shown: Project Operations: Not included This feature is not there in Project Operations as it has OOB integration with Project for the web. 3] Constraints – Start no earlier than, finish no later than: When you add a constraint on the tasks it forces you to start or end on that date even if the schedule is changed. Constraint is very useful, but one needs to be careful about the dates Project Service Automation: Not included This is not available in Project Service Automation and is possible if integrated with Project Desktop Client. Project Operations: ✔️ Included This feature restricts the resource to complete the task start and finish the task in the given time. When a constraint is set your calendar icon gets a cross sign stating that it is restricted. Example: If you select Constraint type as ‘Finish No Later Than’ and the Finish date is set as 3rd February 2023. The task then needs to be completed by the specified date. 4] Milestones – Tasks with zero duration: Milestones are key points in the project timeline and serve as markers to indicate that certain objectives have been met and provide an opportunity to review and assess progress. Milestones are typically used to track the progress of a project, to communicate with stakeholders, and to help manage risks. Project Service Automation: Not Included This feature is not available in PSA and is exclusively available in Project Operations Only. Project Operations: ✔️ Included Adding a milestone task with zero duration is now possible in Project Operations unlike PSA. Just add ‘0’ in the duration field and set same start and finish date as shown below: And now the milestone symbol can be seen as shown in the below image: 5] Resource driven tasks will respect the availability of assigned resources Resource-driven tasks are scheduled based on the availability of the resources assigned to them. This means that the start and end dates of a task are determined by the availability of the necessary human, equipment, or material resources. This helps ensure that tasks are completed efficiently and within the given time frame. Project Service Automation: Not Included This feature is not available in Project Service Automation. Project Operations: ✔️ Included The system considers the availability of resources when scheduling tasks and adjusts task dates accordingly. This helps ensure that projects are completed on time and within budget, and that resources are utilized efficiently. It takes into consideration the work hour template of the assigned resources and changes the Start and Finish date according to the availability. 6] Time-phased editing – Edit plans and work on a day-by-day basis This feature provides a detailed view of the project schedule, with tasks and their associated work broken down into daily increments. This level of granularity enables project managers to adjust the project schedule based on daily progress and to account for changes in resource availability or task dependencies. Project Service Automation: ✔️ Included With the help of this feature, we can change the efforts on the resource assignments grid on a day-by-day basics and even by week or month. This makes work easy as changes can be done on the grid itself. Project Operations: Not Included This feature is not yet added in the Project Operations, but we can expect this update in later phases. 7] Automatic/manual scheduling – Use the Project scheduling engine to schedule tasks automatically or manually Project Service Automation: ✔️included The scheduling of tasks for leaf nodes is determined by the task mode. Every activity supported by PSA has two task modes: automatic scheduling and manual scheduling. Automatic Scheduling: Scheduling engine uses the rules on task attributes to determine the schedule for the task. Manual Scheduling: It stops the engine from calculating the values of other scheduling attributes. Project Operations: Not Included This feature is not available in Project Operations. 8] Edit large projects directly in the user interface: There is no limit to the size of plans that are editable Project Service
Boost Cloud Flows with Process Insights
Problem Definition: Building cloud flows of acceptable quality, should be in the mind of every Power Automate developer. After hearing this guideline, one would naturally ask what makes a flow ‘good-quality’. Furthermore, how can we be aware whether a flow is working up to its full potential? This blog shall provide the answers to these types of questions. After all, our goal is not only to automate processes in Dynamics 365, but to make them efficient – every connector used should serve a purpose, that the flow cannot do without. To begin your cloud flow investigation, first start off with a sample cloud flow. Solution: Once you are done opening your cloud flow in Power Automate, click on ‘Improve your flow’. Your cloud flow will keep track of its run history – This can help you analyze if your flow has improved, or if any new issue has been discovered during the different runs of the flow. Once clicked on, the flow’s downloading process will start. After the download is completed, you will see a pop-up stating your report is ready. A Power BI dashboard will be opened, where you can see all information about your flow, such as a flowchart, average case duration, the custom attributes that have been used and much more! Interestingly, you can even add your own custom filters if you want to keep track of differences among different versions of the same cloud flow. The screenshot below can give you a better understanding on how the dashboard will look like. Out of all the components of the dashboard, let us explore the flowchart in better detail. Notice how your flowchart will contain nodes and arrows, highlighted differently, with different thicknesses and will be marked with labels and number. Here is a brief explanation of the meanings of the labels. An arrow with a greater thickness indicates that the step is frequently executed, as compared to steps which have a thinner arrow. In addition, the darker the node, the longer will be the execution time. As far as the labels are concerned, the number at the top indicates the number of seconds it took for a particular step to execute, and the percentages show the probability of visiting a specific node. Consider the Following Points: Conclusion: To fully understand how the ‘process advisor’ works, just play around with the dashboard, and try using it on any flow that you currently have on your CRM environment. Then, try making minor changes on the flow, and notice the changes that take place in the dashboard. Jot down your observations and make gradual improvements, when inspecting the next cloud flow given to you. Happy learning! References Used: https://docs.microsoft.com/en-us/power-automate/task-mining-tutorial Thank you, Tanmay for your inputs.
Searching on a table is easier with Dataverse Search in Dynamics 365 CRM
Introduction: In Dynamics 365 CRM, we have different search options to search data. As we have hundreds of records of different table, Relevance Search aka Dataverse Search is a global search box that gets the record information across all the tables. There is a new feature introduced in 2022 release wave one for Dynamics 365 CE on Dataverse search. This feature will help users to search & filter for records in model-driven Power Apps. This will make Dataverse Search easier than before to find the data. Description: What is Dataverse Search? Dataverse Search is a great tool to find quickly records across all the tables. It delivers fast and comprehensive result to all tables, sorted by relevance. In model-driven apps, this Search Box is available in the header in the environment. If we opt into early access of 2021 release wave 2 on a production environment, Dataverse Search is enabled automatically. But if not, we need to enable the Dataverse Search. How to Enable & Configure Dataverse Search: – Before Enabling Dataverse Search: – After enabling Dataverse Search: – Dataverse (Relevance) Search is used by the Dataverse Search Index. You can manage & configure the index from the Overview section of a solution. Under Manage Search Index: – It will show us all the tables which are present in the current solution. When users select the tables for indexing, it will show the number of fields that are included in Dataverse Search. These columns are dependent on the Quick Find View. The limit for Columns indexed in this environment is maximum 950 per organization. Users can enable or disable indexing for a specific table from here and can adjust which columns are included in Dataverse Search within the Power Apps portal. Conclusion: With this new update in 2022 release wave one for Dynamics 365 CE, it is just easy to find the record, it also helps minimize the no. of clicks required to find or to get there. References: – Thank you, Shubham Dhumal for your inputs.