web
You’re offline. This is a read only version of the page.
close
  • Service object relation change price

    On Service orders, when a Service object relation is created and afterwards transferred to the service order line, the price changes to the one for the service object an overwrite the price of the item in the line. This does not happen when the service orders are created from a service agreement in which a service order relation has been previously created.
  • Sales Order input returns BOX API error

    When importing Sales Order Header, system returns a BOX API error and it's not creating record When we tried to create a sale order using the entity SalesOrderHeaderV2 with Excel received an error message. Error Message:BOX API can't be used from non-interactive sessions.
  • Product has been released to a company and cannot be deleted

    When deleting a released product using the "Released Products V2" entity, the "released relation" is not deleted from the Product master. This wrongly remaining "Released relation" prevents us from deleting the product master.
  • Purchase requisition update access

    Can we assign access to other users for updating purchase requisition created by someone(creator of purchase requisition) ? Explanation:either you are the preparer and edit the purchase requisition, or you are the preparer on behalf of someone else or you add a reviewer that can edit current lines but not add new lines.
  • Intercompany sales returns synchronization issues

    For intercompany returns, it is not possible the use different disposition actions for the original sales return and the intercompany sales return. Due to synchronization of both orders. The combination of disposition code for crediting the customer in the selling company and return order with intercompany purchase order and intercompany sales order. To overcome this is to handle the return order separately, make sure the intercompany purchase order is not generated. Receive the return item. Create manually an intercompany purchase order to return the item to the delivering company with a negative value.
  • Advance action with a date from the past

    Master Planning generates advance actions which want me to advance some actions to date from the past. It's illogical I think. The earliest date to which it should advance anything is a date of master planning.
  • New inventory dimensions through extension is ready for intercompany transaction.

    In our implementation project we added new four trace dimensions using the standard extension framework. Here the link to documentation: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/inventory-dimensions We need to know if the framework supports inheritance of extended dimensions through intercompany transactions. The Batch dimension is inherited by the purch line transaction (and the related record in inventBatchTable is created if the batchid doesn’t exist in destination company) We expect the same behavior from the new added dimensions using the standard extension framework
  • Zone based replenishment does not work for product variant queries

    Description of problem: All our items are predefined product variants due to which we are not able to utilize the zone threshold replenishment feature. Error message: Zone based replenishment does not work for product variant queries.
  • Zone based replenishment does not work for product variant queries

    Description of problem: All the items are predefined product variants due to which,they are not able to utilize the zone threshold replenishment feature. Error message: Zone based replenishment does not work for product variant queries
  • Partner was unable to use these entities Service order header and service order lines to import and export.

    Description of problem: Partner was not able to use standard data management to upload service order header and lines Error message: Field 'Service stage' must be filled in. Results. Validations failed while writing entity record One or more configuration key in the data entity is disabled. The disabled field(s) 'ServiceOrderStageId' will not be available for use.