Comments
This issue creates inconsistencies which Business Users latch onto and causes distrust of the data. With the newer advances of Synapse Link / Fabric Link and capabilities within fabric, including the new deltalake change data feed, a cascading update solution could be built.Stating the lookup fields are not supported in a FAQ document is NOT sufficient. We went around for 3+ months on a support case, trying to figure out why Fabric Link had data mismatches from CRM. It took months until a tech finally pointed out the small entry in the FAQ which has been slightly revised since this happened now: https://experience.dynamics.com/ideas/idea/?ideaid=56c55490-151a-ee11-913b-0003ff4588ed#submit-commentThis needs to be front and center for anyone enabling Synapse Link or Fabric Link for Dataverse / CE. It needs to be made clear what fields are lookup fields and that they may be wrong. I would have honestly preferred that the fields not be presented at all via Syn/Fabric Link if they could be inaccurate.Users need this data to be accurate and we would like to ask the Microsoft takes further steps to ensure accuracy.
I would prefer that this was either a Company Parameter OR, even better, a setting on the Purchased Item's Coverage Group. Some may want to get an Alert that the PO needs reconfirming so that they can address new date mismatches rather than just an Action message. Unfortunately, most Manufacturers are not on top of Action messages, ignore them, or even have them switched off.
This idea would be very interesting for the Essentially license and the assembly orders, since I’m implementing the “assemble-to-order” functionality for my clients, but there’s no standard solution for sales return orders. I think it’s more than necessary, otherwise the functionality remains incomplete.
This idea would be very interesting for the Essentially license and the assembly orders, since I’m implementing the “assemble-to-order” functionality for my clients, but there’s no standard solution for sales return orders. I think it’s more than necessary, otherwise the functionality remains incomplete.
I fully support this suggestion. The ability to configure the idle session timeout directly from the Business Central Admin Center would be extremely beneficial for administrators. Different organizations have varying security and operational requirements — some may need shorter timeouts for compliance, while others may prefer longer periods to reduce disruption for users working on lengthy data-entry tasks or reports.Allowing configurable idle session durations (within a secure range) would provide both flexibility and control, aligning Business Central with other Microsoft cloud services like Azure and Dynamics 365 CRM, where session timeout policies can be managed by admins.This enhancement would improve user experience, security governance, and overall administrative control within Business Central SaaS environments.
This feature is very crucial for customers where foreign currency is accepted as the tender in their stores.It will be easy for cashier to give a change due in foreign currency and denomination counting also can be done in foreign currency and there by bank deposit also happen in foreign currency.Store local currency is PLN and 1 EUR = 4 PLN, example- Here transaction amount is 16 PLN and customer paid 5 EURO's.Actual behavior - Change due is shown in local currency (4 PLN) but Expected behavior - Change due should be shown in EURO currency (1 EURO). There should be option to show change due dialog box in EURO instead of local currency and update the transaction entries accordingly.