Comments
I agree with the original post - there's nothing in the UI that tells the end user a merge will fail, often because of different Parent Customer (Account) records on the Contact. A pre-check on at least that step would be very helpful, if not the ability to switch back to synchronous merging in the settings.
This would save several of my clients a lot of time because they value both the quantity field and the unit price field for their two-way matching scenarios. When the quantity does not match on the pending vendor invoice exactly to the PO line then there is a quantity discrepancy the posting fails. Manually updating the related purchase order every time with over and under delivery tolerances requires too much manual labor. There should be a way to default delivery over and under tolerances for each procurement category configured. Is there any update on this?
We have the same request with the clarification that we are using Purview Sensitivity Labels for encryption of our emails. We would like Microsoft to work with Microsoft internally to enable inline decryption when tracking emails in Dynamics that carry encryption via Purview Sensitivity Labels.
I agree with this suggestion. It is extremely difficult to have a conversation about Booking Statuses when one is entering a value for "Name", which the user thinks of as the Booking Status, to then have a field called "Booking Status" on the same record, with a separate list of values. Couple that with a column named Field Service Status that is ambiguous and a default view for the Booking Status table named Active Field Service Statuses, and there is just general confusion when trying to work with this table.
In the first versions of Business Central, all users was imported when the sync. to MS365At the time we had to create a specific user for pr. professional (this is done automatic today)Now we are not able to delete these users, although they no longer exist i MS365, and they have not been used for any type of posting.Could also be nice to be able to delete users with entries, perhaps in a date range
We saw this behavior with a client recently. It was a pain point but we have a work around in the interim. Basically we have them Post the Fee as a Customer Charge (Miscellaneous Charge)ConfigurationCreate a dedicated Charge Code Accounts receivable → Charges → Charge codesExample: Code: CC_FEECharge category: Fixed or PercentMain account: Payment Fee RevenueSales tax group: As applicableDo NOT use AR Payment Fee setup for customer-paid fees Leave AR Payment Fees only for company-paid merchant feesTransaction FlowCustomer Payment Journal Apply payment to the invoice onlyBank reflects actual deposit receivedApply Charge to Customer Use: Customer → Transactions → Maintain charges or Add charge directly to the invoice before settlementResulting Posting Debit: CustomerCredit: Payment Fee RevenueNo bank impactNo manual settlement required