A critical issue when importing new costing sheet nodes using the "Costing sheet nodes and absorption basis" entity.

The problem arises when parts of the costing sheet fail during import, whereas importing the full costing sheet results in the deletion of all existing costing sheets, including rates.

Additionally, using the "Costing Sheet Node Calculation Factors V2" entity causes rates to be in a pending state, leading to the deletion of old rates, which disrupts report accuracy.

This issue has been acknowledged by the product team and is noted as "By design" in the official documentation.

Specifically, when importing the cost sheet node entity, the existing cost sheet is entirely deleted before the new costing sheet is saved.

To address this, we propose changing the validation process during entity import to allow partial imports without deleting existing data. This change is crucial for maintaining data integrity and ensuring accurate financial reporting.

Moreover, if new indirect costs or rates need to be imported, the current issue necessitates significant manual work, further complicating the process.

It will be great to reconsider this design and implement a solution that preserves existing costing sheets and rates during the import process.

For more details, refer to the issue highlighted by the product team: https://fix.lcs.dynamics.com/Issue/Details?bugId=606746

A very common requirement that comes up on many projects and especially wholesale distributors is the need to store and see sub-totals along the various levels within the Pricing Tree. I view the Pricing Tree as essentially the Costing Sheet for Standard Cost but the Pricing Tree is for how the Selling Price has been calculated.

Here is an example:

Let's say we buy something for $1,000 from the Vendor. The company decides they want to utilize two Margin Components to Mark Up the Cost along the way to the final selling Price. They determine they want one for 10% to cover corporate Procurement and Marketing expenses and another 2% for inbound Freight. They would like to see this $1,120 as a sub-total in the Pricing Tree labelled as "Sales Cost". This Sales Cost is what the salespeople are allowed to see and all commissions and store level profitability is calculated from Sales Cost to Selling Price instead of all the way back to the actual Financial Cost. Some organizations require to display some of these sub-totaled layers in the Pricing Tree on reports and invoices so it would need to be a stored value to utilize in reporting. Additionally, they often want to allow further Discounts, Rebates, etc. pointing at one of these named/stored Sub-Totals. For example, the customer might get 24% markup from Sales Cost but then 2% off Selling Price for using the private label credit card and a 5% Vendor Rebate leverage another layer in the Pricing Tree.

• Allow for the insertion of named Sub-Totals in the Pricing Tree
• Store these Sub-Totals to leverage on reports and other processes
• Allow these various Sub-Totals to be pointed at throughout other Pricing Elements so the Margin Components, Discounts, Rebates, etc. can access different layers of the Pricing Tree.

When you receive a PO order by using a Voyage (then a Good in transit) it’s very important to generate quality order only for the vendors that requires a quality check. 

but currently we only have following three types: sales, Purchase, Route operation are support for account code, Vendor selection is not enabled for Goods in transit order.

This is very critical for customer business, for example: for the same item I can have 2 vendors, 1 internal and 1 external, I must have the possibility to automatically generate quality orders only for the external vendor.

POs received by using the Good in transit are like normal PO and will need to have the possibility to manage different quality association per Vendor. This is very important for all our customers that are using the “Landed costs” module and the “Quality management”.

Setup hierarchy levels/sequences for applying planned order types to fulfill demand.

Businesses that utilize the same materials across multiple sites and warehouse often purchase material that may already be stocked in another location.

It would be incredibly beneficial if planned order types could be sequenced so that I could plan to transfer material if inventory is on hand in another site/warehouse and not pegged to any demand. If no inventory is available (and not pegged to any existing demand order), the system would use a planned purchase order type instead.

This function allows businesses to consume already purchased/stocked materials across their organization before purchasing additional material. Assuming inventory is available, but the planner does not want to transfer material, they could simply override by changing the planned transfer to a planned purchase order. This manual override is far easier to manage than checking all on hand inventory for every part prior to order firming.

In order to import in mass documents attachments on released product variants it would be necessary to have a data entity.

It would be the same data entity than "Released product document attachments" but for variants.

The data entity should be for imports and exports.

It is not possible to enter items in quotations or sales orders via the product search (product name) if the product name is longer than 20 characters and several products start with the same product name. This will result in the wrong product being entered in the quotations and sales order lines. However, it is possible for items with more than 20 characters to be created as a product.

The following ticket has been risen :

https://fix.lcs.dynamics.com/Issue/Details/1619062?kb=4583258&bugId=506965&dbType=3&qc=8ee06646493f93667e4a4bf105a7d3c8a6cc88a06252706e217a6b11695203f6

506965

Unable to post packing slip for Project purchase order return when negative physical stock is not allowed

Currently, it is not possible to post a packing slip on a project purchase order return, if the negative physical stock is not allowed.

Even if the operation is "neutral" (-1+1) due to the project sales order (item requirement).

The issue is supposed to be settled, but we can see it is not working. (MS bug risen : TrackingID#2410071420002627)

the pop message of counting reason code didn’t appear when you use “adjust in ”  warehouse mobile

application menu and to choose the reason code you should click on the counting

reason code and edit it and then you can choose it from the 2^nd screen.

The pop message of counting reason code should appear 

when you use “adjust in ” warehouse mobile application menu in the same screen as “adjust out “

menu because they have the same setup

Title: 

Improve Product Image Quality in D365 Warehouse Mobile Application

--------------------------------------

Description:

Issue: The current design of the D365 Warehouse Mobile Application (WMA) only supports displaying product images in thumbnail format. This results in low-resolution and blurry images, which can negatively impact user experience and operational efficiency.

--------------------------------------

Impact:

• Users are unable to clearly view product images, leading to potential errors in product identification.
• The overall user experience is diminished, affecting satisfaction and productivity.

--------------------------------------

Proposed Solution:

• Enhance the WMA to support higher resolution images without compromising performance.
• Provide configuration options to allow users to choose between different image quality settings based on their needs and network capabilities.

--------------------------------------

Benefits:

• Improved accuracy in product identification.
• Enhanced user experience and satisfaction.
• Increased operational efficiency.

--------------------------------------

Conclusion: 

Addressing this issue will significantly improve the functionality and usability of the D365 Warehouse Mobile Application, benefiting a wide range of users.

The tracking number groups have been the same options for years and most customers that require batch/serial numbers to include other options like, item number, product code, or just a custom code. If we could select other fields and order of said fields to use for batch/serial number creation would be helpful to avoid customizations at almost every customer.

Example:

• Customer A
• Item number then Sequence Number
• 11129A-0001
• Customer B
• Item number then Reference Number then Sequence Number
• 87462-PRD0001-0001
• Customer C
• Custom code - Sequence Number
• 943-0001