0
Category:
STATUS DETAILS

Comments

REMARK: Including Incoterms codes.

Category:

We have clients who operate in multiple countries and pay us in multiple currencies. It is for this reason that the suggestion to use customer document layouts (word layouts) would not be sufficient to address this need.

Category:

Would definitely like to see the getting added!

Category:

Surely localisation for non-US users is on the roadmap for Customer Voice?

Category:

It would be great if the G/L Reconciliation report can allow filter the Inventory vs G/L differences per
Location,
Inventory Posting Group and
Gen. Posting Group

If you add a Location, the report does not show the differences in G/L. So this report only show the G/L differences without adding a Location.

Category:

This functionality has existed for ages. The Idea is obsolete and should be closed.

Category:

REMARK: For purpose of item identification of (e.g. translations, weight, country of origin, default broker (s), broker translation, international code, exchange rate, eligible transportation, eligible incoterms, etc.)

Category:

Procurement team has always to approve the purchase order, either through direct delivery or receive goods in own stock. This is our business rules, Nothing is ordered and confirmed without approvals. All our procurement transactions are supported by Workflows.

Category:

Agree, this would be practical as the entity lookup table enables only one entity (Y)

Category:

Thank you for your suggestion.
We plan to improve the B-to-B scenarios around segments and exporting them. Your suggestion fits into this nicely. Once we know if and when this is planned, we will announce it in our release plans: https://docs.microsoft.com/en-us/dynamics365/release-plans/

Category:

  • 1
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 500