0
Category:
STATUS DETAILS

Comments

We utilize BC for 5 different companies and use the Inter Company function directly in the Purchase Orders and Purchase Invoices but the Sales Tax does not follow the entry and ends up staying the originating company which is incorrect. There is risk to the Sales Tax not being transferred over manually as our AP system is now mostly automated with AI and there is no efficient process for being able to review IC entries posted entries and manually transfer the Sales Tax amount with an IC Journal. We would be very appreciative to have the IC function fully account for transferable taxes between companies.

Category:

Dear Mr. Totovic - are you aware that the mentioned migration routine is changing current data in the swiss-version of D365 BC so it becomes unusable/wrong after the migration to BC28? I think the new FCY-Module should be postponed to be automatically activated in BC28. We tried to explain the circumstances to the support-team but they did not understand the case.

Category:

Is any from Microsoft reading this ? If we don't get a solution soon we can not sell our solutions after 1. August 2026 (where the current certificate expires)

Category:

Also, it would be great if the workspace had different views, for instance a view for preview features, a view by country etc.At least, we should be able to create or own views in the workspace.

Category:

From a compliance perspective, I think we should be able to prove to the auditors that we have deliberately chosen not to deploy a feature, so a function to give a feature a governance state would be ideal. This should come with an audit trail, so the lifecycle of a feature can be documented.

Category:

THIS. please fix. It's causing SO much headache.

Category:

Pleas fix this. It's making our jobs so much more difficult than it should be.

Category:

This is mentioned documentation. https://learn.microsoft.com/en-us/dynamics365/customer-service/use/use-customer-support-swarming

Category:

Utilizing nominal weight instead of actual weight for master planning is highly detrimental for any business that produces catch-weight products. In industries such as meat processing, weight variability can be significant, making reliance on fixed (nominal) weights inherently inaccurate. These variances introduce meaningful downstream impacts across the operation.Under the current system structure, this issue is driving substantial lost sales, as planning outputs do not accurately reflect true available supply. This directly impacts customer fill rates and OTIF (On-Time In-Full) performance, ultimately eroding overall customer confidence and service levels.In addition, the misalignment between nominal and actual weights leads to consistent overproduction. Master planning is effectively overscheduling, resulting in excess finished goods inventory. This, in turn, contributes to increased shrink and associated financial losses.It is also important to recognize that the meat business is inherently seasonal. Fluctuations in demand throughout the year—driven by holidays, weather patterns, and grilling seasons—impact both production requirements and the size of primals. This seasonality further amplifies variability in weights, making accurate, actual-weight-based planning even more critical. Without accounting for both variability and seasonality, planning inaccuracies are compounded, increasing operational inefficiencies and financial risk.

Category:

I agree! Its not naturally intuitive to have to select the three dots for more options. I would hope users are reviewing the full document before approving or rejecting, so it makes sense to have it being a more prominant button!

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500