• 14

    The inventory status field is disabled and cannot be modified when using the transfer journal for non-WHS enabled locations.

    We need to move 3 damaged items from Location A (Floor) to Location B (Damaged Items) and update the inventory status from 'Available' to 'Damaged'. However, this task cannot be accomplished through the browser.

    in addition, the "On-hand by location" form allows changing the inventory status, but it does not permit specifying the quantity or location.


  • 14

    Cannot create a record in Purchase order header information for Intrastat (PurchTable_Intrastat)." Reference xxx. The record already exists." when modifying PO header in Czech legal entity

    Suggested by Youssef Eissa New  0 Comments

    Introduction: 


    encountered a significant issue affecting the operations when using the Czech legal entity in Dynamics 365. This Issue impacts the creation and updating of purchase orders, leading to errors that disrupt our business processes.


    Problem Description: 


    When attempting to create a purchase order and update any field within the PO header, users receive the following error message: "Cannot create a record in Purchase order header information for Intrastat (PurchTable_Intrastat). Reference: xxxxxxxxxx. The record already exists." This issue has been identified as a bug by the Product Group.



    Workaround: 


    The Product Group has suggested the following workarounds:

    1. Refresh the newly created purchase order before making any updates.
    2. Create purchase orders from All Vendors > Choose Vendor > Procurement > Purchase order.
    3. If the error occurs, duplicate the current browser tab and reopen the purchase order.

    While these workarounds provide temporary relief, they are not ideal for long-term use and can be cumbersome for users.


    Request for Consideration: 


    We understand that the Product Group has determined that this bug does not currently meet the criteria for an immediate fix. However, we believe that addressing this issue is crucial for improving the overall user experience and ensuring smooth business operations. We kindly request that this bug be reconsidered for a future fix, taking into account the impact on users and the availability of a valid workaround.


    We appreciate your attention to this matter and look forward to seeing improvements in future updates.


  • 14

    Purchase requisition entity is not usable for dual write

    Suggested by Ibrahim ElGamal New  0 Comments

    The data entity Purchase Requisition V2 is not usable for dual write or integrations because of validation if the worker (Preparer) is equal to the worker assigned to the user.


    when you use dual write or oData to create a record, you will use an app registration. This app registration has in Dynamics 365 FnO a (generic) user connected. But this user doesn’t have a worker assigned. You want to populate the Preparer with each worker that exist in the legal entity.



    The data entity validates if the worker assigned to the user is equal to the worker specified in the field “Preparer”. From a data management perspective this is very logic. You don’t want that another worker requests a purchase on your name. But from an interface perspective (oData, Dual write) this is not possible. Those will use an app registration that is related to a user that has no worker assigned. Even if you assign a dummy worker to the user, you don’t have the traceability who created the purchase requisition in the external app.



    As a workaround:


    Extended the Purchase requisition entity and customized the field "preparer" by disabling it's validation





    Summary; This validation should only be executed for the Excel add-in or data management. But not for Dual Write or oData.




  • 14

    Ability to use external scanner on Asset management app, instead of built in camera

    Suggested by Geert Van Zeir New  0 Comments

    I understood that it is currently not possible to use an external scanner (e.g. wired or Bluetooth) on the asset management mobile app. There is only the option to either enter the (item) codes manually or to use the camera of the mobile device itself. Using the camera is extremely un-accurate for aiming at the correct barcode and unpractical in many cases: e.g. our customer docs the tablet onto a cart and would use the external scanner to confirm the scanned items (some of these products are stacked closely together, so aiming for the correct barcode with the device camera is a nightmare). A handheld scanner would solve many issues.


  • 14

    Allow customization on Approvals Management mobile

    Suggested by Mathieu Binaisse New  3 Comments

    It will be great if Approvals Management mobile's UI can be customized.

    Adding fields, personalize designed ...


  • 14

    Intercompany between 2 different tenants

    Suggested by Ayman Ali New  1 Comments

    We would like to have an option to do intercompany between 2 separate tenants.


    It'd be an important perk for Big/large companies with multiple branches and departments where a department can be acquired by a different company, but we want to maintain the trade relations between them. And vice versa, we can merge 2 companies together and each of which will have its own tenant and maintaining the trade flow is required.


  • 14

    Landed cost: Shipment / container creation should be a 2 step process as option

    Suggested by Jan Cavens New  0 Comments

    Currently, it's during voyage creation that the voyage AND containers are created in 1 go.

    However, our customer's process is:

    1. Shipment booking at forwarder
    2. When shipment is done at vendor or subcontractor (for TO's) containerization is done where exact container contents (products, quantities, variants, ...) are registered.


    In the landed cost voyage creation process, this is not possible since voyage lines can only be created when container is defined.


    Workaround would be:

    1. Create shipment + add all lines to dummy container
    2. When container content is known: Delete all voyage lines and create new voyage lines with correct containers.
    3. Voyage data entities can't be used, since you can't overwrite the container in the line entity (read only)

  • 14

    [BRA] - Separação e Recebimento de Produto via Ordem de Transferencia que sejam executadas pelo WMS

    Suggested by Cristiane Ferracini New  0 Comments

    O processo de Ordem de transferencia não esta interligado ao WMS. Quando se faz a separação via WMS e faturado a nota pela localização brasleira, ao cancelar a nota, o Item e o Trabalho criado não são estornados, impossibilitando um novo faturamento.


  • 13

    Item substitutions (plan group) are not considered when formula line is replenished through transfer requirement

    The customer is using item substitutions (plan groups) on formulas that consist of two lines, each with its own priority. The primary and secondary formula item have corresponding item coverage setup that replenish demand with planned purchase orders at warehouse 12 and transfer this demand to warehouse 13. However, when planning is run with demand at warehouse 13 the system completely ignores plan group setup. It covers the demand with on-hand inventory and replenishes the remaining quantity only for the item with priority 1, without considering the on-hand inventory for the item with priority 2. However, if the demand is for warehouse 12 (where no transfer is required), the item substitutions work as expected, and the on-hand inventory for the item with priority 2 is considered.


  • 13

    My quotations go to All quotations after refresh when enable Sales quotation details performance enhancement.

    Suggested by Ke Ji New  1 Comments

    My quotations go to All quotations after refresh when enable Sales quotation details performance enhancement. Customers wait to keep on My quotations page as only need to do business on my quotations.