Real-time collaboration using Coauthoring in Canvas App
The 2024 Wave 2 release includes a notable feature for developers creating canvas apps: real-time collaboration using Coauthoring. What is Coauthoring?It was previously forbidden for many creators to edit an app at once. Coauthoring allows developers to quickly author and amend a canvas application. By facilitating rapid collaboration and app development across multiple makers, this experience expedites and saves time during the app development process. When several makers are needed, this functionality also improves code reviews, debugging, and training.A canvas app can be edited simultaneously by multiple developers. In the past, Power Apps Studio copresence experiences allowed numerous developers to collaborate on a canvas application, but only one developer could make changes to the app.With the new coauthoring functionality, multiple developers may work together to edit a canvas app simultaneously, much like they can with Microsoft Word and PowerPoint. With the help of this feature, fusion teams may enhance their Power Apps Studio collaboration and expedite the app development lifecycle. In real time, makers can also view the updates and whereabouts of their coworkers.How to Enable Coauthoring?Coauthoring supersedes the copresence functionality once it is enabled.To enable coauthoring, follow given steps: What are the Limitations of Coauthoring?• When multiple users are editing the application, the following settings are not available: ➢ Search ➢ Save as ➢ Open another or new app ➢ Undo and redo ➢ Switch authoring versions ➢ Depending on whatever restriction is reached first, up to 10 coauthors may be added in a single session or over the course of 10 tabs. Beyond 10, any more coauthors or tabs will be in copresence and won’t be able to edit the app or receive real-time updates. ➢ When an app is opened for editing, the language of the application is locked to the first user’s locale. ➢ Cut is disabled. ➢ Coauthoring is disabled in the Monitor tool. • Issues could arise from the following actions: ➢ When you try to rename a control ➢ When you add AI Builder components ➢ When you add geospatial controls ➢ When one author adds a flow and another coauthor tries to run the flow without first refreshing the app ➢ Some errors from one author’s actions are visible to all other coauthors ➢ When you copy and paste Conclusion:This improvement facilitates teamwork and speeds up development processes by enabling several users to work concurrently on the same canvas app. Teams can expedite the app-building process, share ideas, and give prompt feedback with real-time updates and collaboration tools. This function is revolutionary for companies trying to boost output and encourage teamwork among their development staff. Thank you, Arvind for your valuable inputs for this blog!
Explore Dynamics 365 Sales vs. Sales piece in Project Operations: Crucial Distinctions to Remember
For most organizations running on Dynamics 365 (D365), the traditional Sales module and the specific Sales in Project Operations are some of their best options of choice. These solutions are designed to serve distinct purposes that are aligned with different business needs. In this article, we will delve into various particulars of these differences, or more specifically, what the Sales module has that Sales in Project Operations does not and vice versa. Dynamics 365 Sales: Towards More Efficient Product-Based Services and Relationship Management Dynamics 365 Sales is targeted towards product-based services and all-encompassing relationship management. The following are its distinguishing features: Sales in Project Operations, on the other hand, is appropriate for companies whose sales procedures are closely related to project management and service provision, such as: Whereas Dynamics 365 Sales is focused on sales team activities and basic tracking related to sales transactions like manage leads, opportunities, and customer interactions for product sales. Dynamics 365 Project Operations includes project planning, resource allocation, and financial tracking for service-based projects. It is used for Comprehensive management for project teams, including scheduling and utilization and detailed fiscal management, including project budgets, costs, and billing. BUSINESS SOLUTION: How to Choose the Right Solution for Your Business: Choosing between Dynamics 365 Sales or Sales in Project Operations depends on your industry focus, business model and specific operational needs. Therefore, if you are running a product-based business that requires advanced sales management capabilities such as relationship analytics, goal management among others with LinkedIn and SMS providers integration then you should opt for Dynamics 365 Sales (Sales Hub). On the other hand, if your firm operates within project-oriented sectors that require highly integrated selling procedures revolving around resource planning and project management, then you should go for Sales in Project Operations which comes with specialized tools that cater to these requirements exactly. CONCLUSION: Project Operations focuses on integrating sales operations with project management, whereas Dynamics 365 Sales handles more comprehensive CRM features and product sales management. Project operations serve the demands of sectors such as manufacturing, construction, and professional services, where project delivery and service execution are vital to sales success. Thanks, Kalyani for your valuable inputs!
How to Set up OneNote integration in Power apps
Introduction: Enabling OneNote integration to provide the advantage of seamlessly incorporating OneNote for capturing or revisiting customer notes directly within our records. This integration can be configured alongside SharePoint Online, but it requires a Microsoft 365 subscription for leveraging OneNote functionality within model-driven and customer engagement apps. Steps to Turn on OneNote integration. Implementation:
How to use Flexible Height Gallery in Canvas App
In Power Apps, a flexible height gallery is a dynamic container that shows a collection of data. Based on the information it contains, it dynamically adjusts its height to fit different types of data. By adapting to various screen sizes and presenting data in an organized way, this aids in the creation of adaptable and aesthetically pleasing interfaces. Steps to Implement Flexible Height Gallery Note: Conclusion: 1. Responsive Design: Flexible galleries adjust fluidly to various screen sizes to ensure that images are shown appropriately and proportionately on platforms ranging from tiny smartphones to giant desktop monitors. 2. Better user experience: Viewing images doesn’t require users to zoom in or scroll far. 3. Cross-Device Compatibility: With flexible galleries, your material is available on many platforms, including smartphones, tablets, laptops, and desktops. This improves the overall user experience and decreases annoyance, making it easier for visitors to engage with your content. Your potential audience and engagement are increased by this compatibility. 4. Uniformity: Flexible galleries contribute to uniformity in look and feel across devices. This uniformity strengthens your brand identification and gives users a sense of professionalism. Thank you, Vijay for your valuable input.
Critical Path & Advanced Task Dependencies in Project Operations
Problem Definition: As we all know, that the WBS which is visible in Project Operations is based on Project for the Web and the features such as Critical Path and Advanced Task Dependencies are not the part of the Product. What is a Critical Path? The project’s estimated start and conclusion dates are determined by a set of activities, or occasionally just one job, known as the critical path. Task dependencies are the usual means by which the tasks that comprise the critical route are connected. Your project plan is probably filled with several networks of tasks like this one. The project is finished when the final job on the critical path is finished. What are Advanced Task Dependencies? There are different types of task dependencies, the default link type is finish-to-start. However, this doesn’t work in all situations. The other types of links are start-to-start, finish-to-finish, start-to-start. Solution To enable these features in D365 Project Operations, you need to add a Project Plan 3 or Project Plan 5 license with your Project Operations Full license. The features will be available in the Task planning as shown below: Critical Path: The user can examine their project tasks according to the critical route of the project structure by adding one of these licenses. This will be accessible in the timeline view’s filter section. However, this option is exclusive to the person who has the extra license; individuals without will not see it. This feature will highlight all the Project tasks connected to the end date of the Project once you enable it. This includes the depending on work as well. Advanced Task Dependencies: The user will be able to access advanced task dependencies with the same license package. Project Operations only allows you to add Finish-to-Start dependencies by default. Thus, link a task’s Finish Date to the Start Date of the task that comes after it. You can add the “Depends on” column or navigate to the specifics of your task in the grid planning of your project plan. After choosing a possible dependent task, the user is now shown with a little pop-out arrow at the bottom. The sort of dependence can be chosen here. Based on the selected link type the Start/End dates of the tasks are connected. The same menu is available via the Project tasks details. Accessible via the small “i” symbol on the tasks or the three dots menu. Conclusion: With the help of the additional license (Project Plan 3 or Project Plan 5) users can now have the missing features such as Critical path and Advanced Task Dependencies, which is very important for most of the organization. Thank you, Sankalp for your valuable inputs!
Advances and Retainers in Project Operations
Problem Definition: Earlier, milestones were used for advance payments which was not the actual purpose of it. But with the introduction of Advances and Retainers, milestones will only be used for their real purpose on fixed price lines. What are Advances and Retainers? The feature Advances and Retainers are seen on the Project Contract form. Advance payment or the retainer fees both means the same. It is used for an advance payment from the customer/client. This feature can be applied on fixed price as well as on time and material contract lines. Solution: Conclusion: This feature is helpful for an organization delivering the project. Because it provides margin to recover the costs incurred due to any increase in scope that a fixed price contract would not have allowed. Thank you, Sankalp for your valuable imputs.