0
Category:
STATUS DETAILS

Comments

I agree with the comments below. This is a requirement for every client that uses Procurement categories.

Category:

Along with this functionality is the need to override a source warehouse for an item so that master planning creates planned orders in the correct warehouse. Currently the only way to do this is to define a source in each warehouse and then to create an item/warehouse coverage for any items where this is an exception. An item default is needed to eliminate the need to create an item coverage for each warehouse where demand could coming from.

Category:

While updating your Local Chart Of Accounts, section "Consolidation", we need to manually type the consolidation GL Account (D & Cr).

We should be able to select the Consolidated Chart Of Account in the Consolidation Company, in stead of typing it.


We have already linked to the consolidation API.

Category:

I do not agree with this functionality. I would like to suggest that for specific Posting Groups (such Customer, Vendor, Banking, Inventory, Fixed Assets). Once a posting has been done, the system should block you when you are trying to post to another GL account. The problem could raise that your subledgers (example Customer Ledger Entries - AR Aging) doesn't match the GL accounts - Accounts Receivable.

I would suggest to have at least the option in the setup to choose that you want to avoid, to post to multiple posting groups on a customer, vendor, bank, inventory and fixed asset.

The "centralized" gl accounts should also been setup "Direct Posting = No"

In order to guarantee the data compliance

Category:

Our customers intend this field to work as previously as it is easier for us to check the journal account names rather than codes. Though we can identify account by the description, but it will be better if this field can work like before (show account name in AccName field).

Category:

Please, Dynamics 365 is not adapted to Spanish requirements if reports doesn'n split amounts by quarters in Customer Annual Declarations, it will be also helpfull to incloude email and phone number in this report

Category:

The approval workflow currently does not support handling multicurrency purchases effectively. I highly recommend implementing this feature, as it would provide us with the flexibility to map the workflow based on either the amount in the purchase order/sales order header currency or the amount in the local currency (LCY). This feature is essential for the product to remain competitive with other ERP systems.

Category:

it is very common to forget to add the attachment when sending an email. The recall option would be great to have it, so we can recall the email and send it again with the full information.

Category:

I am based in New Zealand and we have successfully implemented the voice channel with our local voice provider using our local existing phone number (country code being +64), so it is possible.


You could reach out to your local phone providers and ask if any of them are Microsoft Teams Phone Partners?

Category:

Have you tried using Azure Monitor? On Microsoft Learn this is under Azure > Communication Services > Enable logs via Diagnostic Settings in Azure Monitor


Category:

  • 1
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 500