Dynamite App Technologies Limited (DAT)

FYI: Microsoft Announcements for Dynamics CRM On-Premises Dynamics CRM 2015 will go out of support on January 14th, 2025. If the OP2OL migration is not planned before January 2025, please request the customer to upgrade to Dynamics CRM 2016 and then reach out to Microsoft for OP2OL migration support. Dynamics CRM 2016 will reach EOL by the end of 2025. Customers are encouraged to complete their cloud migration in 2025. Thank you for sharing Stephan Smith

👯♀️ To avoid your project team and implementation partner disbanding after the post-implementation phase of CRM deployment, consider the following strategies to maintain continuity and support: 1. Develop Long-Term Relationships: Foster strong relationships with your project team and implementation partner from the outset. Emphasize the importance of long-term collaboration and ongoing support beyond the initial deployment phase. 2. Include Ongoing Support in Contracts: When engaging with an implementation partner, ensure that the contract includes provisions for ongoing support and maintenance post-implementation. Clearly define the scope of support services, response times, and service level agreements (SLAs). 3. Establish a Transition Plan: Develop a transition plan outlining the handover process from the implementation phase to ongoing support and maintenance. This plan should include knowledge transfer sessions, documentation of key processes, and training for internal staff. 4. Retain Key Personnel: Work with your implementation partner to identify key personnel who will remain involved in the project post-implementation. Retaining individuals with in-depth knowledge of the project and CRM system can help ensure continuity and stability. 5. Cross-Train Internal Staff: Invest in cross-training internal staff to build expertise in managing and maintaining the CRM system. This reduces reliance on external partners and empowers internal teams to handle routine tasks and troubleshooting independently. 7. Utilize Vendor Support Services: Take advantage of vendor-provided support services and resources to supplement internal capabilities. Most CRM vendors offer support forums, knowledge bases, and technical assistance to help users troubleshoot issues and optimize system performance. 8. Engage in Continuous Improvement: Continuously evaluate and improve the system based on user feedback, business requirements, and evolving industry trends. Regularly review system performance, user adoption, and ROI to identify areas for enhancement and optimization. 9. Maintain Open Communication: Keep lines of communication open with your project team and implementation partner even after the deployment phase. Schedule regular check-ins, status updates, and post-implementation reviews to address any issues or concerns that may arise.

Great new feature for blocking unmanaged customizations! The capability to block unmanaged customizations. This is an environment setting that allows Power Platform system administrators to prevent unmanaged customizations in Microsoft Dataverse environments. By blocking any unmanaged customizations and import of unmanaged solutions, Once the setting is enabled these restrictions will be imposed for the environment: 🎯 Import of unmanaged solutions into the environment are blocked. 🎯 Creation of new solution objects like apps, tables, and forms are blocked. 🎯 Customizing existing solution objects are blocked. 🎯 Any unmanaged customizations changes result in an error returned to the user, such as: “This environment doesn’t allow unmanaged customizations. This was a choice made by your admin, and certain actions won’t be available or will be view only.” The following operations are not blocked by this feature: 🎯 Change of environment variable values. 🎯 Enabling or disabling of solution objects. For example, turning Power Automate flows on or off. 🎯 Assigning of ownership or sharing of table records. 🎯 Solutions operations like remove active customizations. 🎯 Creation and export of unmanaged solutions.

Thank you Microsoft Dynamics 365, for including the above functionality in the 2024 release wave 1 plan CREATE MULTIPLE CASES FROM EMAIL SENT TO MULTIPLE BOXES Business value Creating corresponding cases for all mailboxes to which an email is sent helps agents have full visibility into customer issues. The appropriate team gets the full context and can independently respond to customers’ issues, without having to transfer the case to the relevant queue. This avoids delays in sending a first response to customers, improves average case handling time, and avoids service level agreement violations. Feature details Here are the key capabilities of this feature: Email sent to multiple queue-enabled mailboxes (irrespective of To, Cc, Bcc) gets converted into multiple cases (one case corresponding to each queue enabled mailbox). Email gets associated to each case and is shown on the case timeline. Agents belonging to any of the queues (to which the email was sent to) can respond to the customer independently from any case using the case timeline. Any reply from the customer to the original email gets associated to the case created in response to the original email, instead of creating a new case. If a customer replies to the original email while adding a new queue-enabled mailbox, a case gets created for the new mailbox and the replied email gets associated with the new case in addition to the existing cases. Some of my customers/Partners would be happy to hear this.

Finally! You can now Link Activities with multiple records (Preview) in Dynamics 365 🕴 The Business Value With the introduction of this feature, the Activity records can now be linked to additional records such as Accounts, Contacts, Leads, Opportunities, and Users using the new party list attribute. Utilizing this functionality enables users to link a single activity with multiple records simultaneously, eliminating the need to generate duplicate activities for every individual record.