Dynamics 365 Finance & Operations Developer Needed – Fixing/sync the inventory

1) Purpose Troubleshoot and fix the issue of items that have issue in inventory. This paid task is for evaluation purposes only and does not create any future commitment unless a new agreement is made. 2) Task Description • Task name: Fixing/sync the inventory • Target environments: DEV / UAT / PROD • Summary: We have a few cases where there's an inventory issue, specifically in the inventSum table (On-hand). The actual inventory, which is what we see in the inventTrans table (Inventory transactions - containing all transactions and movements for the item), doesn't match what the inventSum table (On-hand) displays. The table (inventSum table (On-hand)) isn't reflecting the actual inventory (as it should).  InventTrans table (Inventory transactions) - actual inventory (right):  InventSum table (On-hand) - what we have issue here, and we want it to match the inventTrans table as should be (in normal case). This is a rare occurrence, and we only have a few cases. Therefore, what we want is for the affected tables (tables impacted by any transaction on the inventory transactions table, including the available inventory table (inventSum), etc.) to be synchronized or corrected to align with the inventory transactions table - inventTrans table (Inventory transactions). • Requirement: A solution that scans and detects these instances (cases with inventory synchronization issues, where the inventory table inventSum doesn't display the actual inventory InventTrans). We then select the cases to be fixed (we have the option to choose which ones to fixed), and then repairs them with a single click. Afterward, the affected tables (tables impacted by any transaction on the inventory transactions table inventTrans, including the InventSum table (On-hand)) are synchronized or corrected to align with the inventTrans table (Inventory transactions). This solution allows us to detect (find) and fix problematic inventory cases, and it also provides a record/log of all problematic cases (found, or found and fixed, who did it, and when). It's not just about correcting the InventSum table (On-hand); all related and affected tables and elements must be corrected. The developer must be familiar with the nature of the process. For example, when any action is performed on a specific item, the action appears in the InventTrans table (Inventory transactions), and this is reflected in the InventSum table (On-hand) and other tables. Therefore, what happens in real-world scenarios must be simulated and applied here. The developer must have a clear understanding of the business logic, be able to implement an accurate and reliable solution, and deliver ready-to-use outputs. It's not just about implementing and applying solutions; one must be aware of and understand the related and connected aspects that will be affected • Solution: After analysis and investigation, the developer must present a scientific and reliable solution, outlining its advantages, disadvantages, and safety. If the solution is excellent and meets our terms and requirements, we will adopt it. • Prototype: We have a concept and expectation of the final solution (as a user interface, front-end) that we have created as a prototype. (It is not necessary for the developer to implement it exactly; if they can implement it in a better and more efficient way, that would be great. That depends on the developer's skills and experience.)