RE:
Our customer asked for something similar yesterday: "Most CMMS software has the function of start and stop functionality." They are looking for functionality similar to what we have on Production Floor Execution. From the documentation: Use the actual time of registration – Set this option to Yes to set the time for each new registration to the exact time when the worker submitted the registration.
RE:
This is a great idea. Offers more flexibility to buyers to send to a vendor particular contact. A Vendor might have several divisions or satellites and an email on the vendor master record is too restrictive. Using the Contact email address offers more flexibility and does not require to re-forward an email to the right addressee.
RE:
The main gap here is the update to the inbound warehouse after GIT receipt, whether the receipt is through an arrival journal or an allowed update to the inbound warehouse on the GIT order. There are numerous requirements detailing this and would be a big win against other systems with similar functionality.
RE:
We have the same requirement on a current project, the workaround we are using is to build a 'virtual warehouse' at Port which is the warehouse defined on the PO. Goods are then transferred from Port into the network of inland warehouses based on priority of stock in containers, however this solution presents it's own set of gaps. Redirection of inbound goods would be incredibly beneficial and should be considered in the future roadmap.
RE:
I strongly support this idea and would like to add a suggestion for enhancing event management analytics within Dynamics 365. Similar to HubSpot, which encapsulates all event-related elements into a single "container," it would be extremely beneficial for Dynamics 365 to adopt a unified approach to manage invitations, registrations, and attendee tracking. By creating a centralized "event container," users can easily navigate and analyze all related activities and metrics from a single point, which streamlines processes and enhances data accessibility. While HubSpot provides a good model for integrating event elements, Dynamics 365 could further improve by offering superior management of registrations and event access controls. This integrated approach would greatly aid in simplifying event analytics and enhancing user experience.
RE:
I fully agree with Mike Serola's proposal. As a company with over 500k contacts in our CRM and consisting of 10 brands, we find it extremely cumbersome and complicated to manage the prevention of duplicate registrations using lengthy and complex Logic App workflows due to the lack of this functionality in Dynamics 365 Event Management. The ability to prevent multiple registrations for the same contact is essential to simplify operations and improve efficiency. Could you provide us with an update on the ETA for the release of this feature? Its implementation would greatly benefit many users and could significantly enhance large-scale event management. Thank you for your attention to this critical request.
RE:
We have the same problem for several customers. Anchored solutions would be very good solution!
RE:
I cannot understand why this is possible, while a user cannot add a time off within a previous active employment.Imagine there was an accrual frequency change or change into the enrolments of the same Leave Plan due to a FTE change needing un-enrolment + re-enrolment into the same leave plan to calculate the correct pro-rated accrual amount. A user cannot submit any time off request for their previous enrolment.
RE:
Although limiting the number of actions is beneficial for system to process, and for users to troubleshoot when something happens, this limit should still be increased, as marketing campaigns are expected to have many phases.
RE:
It's 2025! Please release this feature.