Comments
Surely the underlying database (SQL Server) isn't the cause here because the maximum unless you are using smalldatetime is 9999-12-31. I understand there will be remediation for existing customers that rely on it being 2154 so perhaps you could make this configurable so those customers not wanting to be locked into the artificial limit of 2154 can freely use up to 9999-12-31 as the underlying database technology supports?
I fully support this. The capability exists in Store Commerce to take a prepayment and if you set the percentage default to 100% as you can do for Customer orders it captures the funds truly as a deposit and only posts the sale when invoiced. The above should work in a similar fashion and it would give us an omni channel solution. I like the ideas that Brian conditional settings however if these could be implemented in Commerce they should be implemented back in Store Commerce and Call Center to have one mechanism of doing prepayments......please!
The PR is merged and available in BC25.4Documentation: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/itpro-introduction-to-automation-apis#unpublishing-an-uninstalled-appYou can find the change here:https://github.com/microsoft/ALAppExtensions/pull/27916
Agree with the other comments. I think a check box with an option not to alert attendees would be ideal. We ended up removing the Required Attendees field from the main appointment window and provided instructions to users about not syncing meetings from Outlook to Dynamics and also removing Required Attendees if using quick create from a contact record.