-
Not flexible Quantity discount promotion
Customer would like to give discount to Product regardless of Variants (eg different sizes of T-shirt). They would like to assign price and discount for cumulated Qty regardless of variant. There was suggested to use Retail Quantity discount promotion instead of Line discount from Trade Agreement. But Quantity discount is not flexible for users. If there is requirement to modify slightly Unit price or Discount % for one product then new Promotion should be created. Retail Quantity discount promotion has some disadvantages like it is not possible to define promotion conditions in promotion lines. This feature exist in Line discount defined in Trade agreement but such Line discount is not cumulative. It was described in 2 RFH: VSTS#216061 - Wrong Line discount from Trade agreement when Sales order generated from Call center and more then one line with the same product VSTS#247182 - Inconsistent behavior - Wrong Line discount from Trade agreement when Sales order generated from Call center and more then one line with the same product It is required either to improve functionality in Line discount defined in Trade agreement or in Retail Quantity discount promotion. *** Steps to reproduce 1. Register Quantity discount 2. If it is required to modify condition for one line/ Product then new Quantity discount promotion should be generated. 3. There should be modified Quantity discount promotion to define conditions like Price or Discount % in lines or new type of Retail promotion should be generated to have similar functionality like it is possible in Trade agreement to define From Qty/ To qty and Price/ Discount % in lines. *** Actual result: If it is required to modify condition for one line/ Product then new Quantity discount promotion should be generated. *** Expected result: There should be modified Quantity discount promotion to define conditions like Price or Discount % in lines or new type of Retail promotion should be generated to have similar functionality like it is possible in Trade agreement to define From Qty/ To qty and Price/ Discount % in lines. -
Data entity for table PdsBatchAttributes does not exist - not possible to import the attributes for a specific batch number
For all our customers in the chemical industry, metal trade, we use the batch attributes to uniquely define the different item batches on stock. We love this functionality, because this eliminates the need to create custom fields on the item batches. Standard Dynamics 365 supports attributes per batch attribute group, and also per batch. We can set this up by hand using the Dynamics 365 user interface. Right now, with the mentioned data entity, we’re only allowed to migrate attributes/attribute values per batch attribute group, not per batch number. FinOps 244137
-
Code upgrade tool fail with vague error. Customers and partners must raise a support request to get the details
Code upgrade tool fail with vague error. Customers and partners must raise a support request to get the details. Microsoft internal reference : One workitem 2641643
-
Issues when syncing to BPM using a custom Azure DevOps (VSTS) process template
When setting up your Azure DevOps (VSTS) project in Lifecycle Services (LCS), if you use an inherited process template with custom fields, you may receive the following warning message: "The selected VSTS project is based on a custom process template. Custom process templates are not supported and may cause errors when synchronizing Business Process Modeler libraries with VSTS. Lifecycle Services supports the standard Agile, CMMI, and Scrum process templates." This idea is to get number of vote for work highlighted in https://blogs.msdn.microsoft.com/lcs/2018/11/28/issues-when-syncing-to-bpm-using-a-custom-azure-devops-vsts-process-template/
-
I need to update the LCS project with detailed project plan from Excel or Microsoft Project.
I need to update the LCS project with detailed project plan from Excel or Microsoft Project. It will help in tracking the project lifecycle. Can only access a simple milestone plan today.
-
Resource name not updated after being modified in Global address book
Whenever customer is modifying the worker name from global address book it should impact the related project resource. This is the product suggestion for Design limitation 427558 -
Add a translation feature for "Main account categories" to simplify Electronic report generations.
Add a translation feature for "Main account categories" similar to the existing ones for General Ledger Account and General Ledger account template so that the user interface become consistent and to simplify Electronic report generations for some legal requirement like Polish SAF Accounting books. -
Add entities related to Databaselogs to allow export.
Add entities related to Databaselogs to allow export. -
CHN: Unable to perform tax adjustment at line level in Project Invoice Proposal
It's not supported to adjust tax amount at line level for project invoice proposal. this idea to add support for it. LCS Issue : 427804 -
Ability to change 'Storage dimension groups' for Std cost products with physical transactions which are not tracked by location.
Ability to change 'Storage dimension groups' for Std cost products with physical transactions which are not tracked by location.