Suggested Tue, 13 Feb 2018 00:12:34 GMT by McKenzi GebhardUnder Review
Category: Inventory management

When adding transfer order lines manually to a transfer order, the line numbers should update and sequence automatically. In the current design, the first line is line number 1 as expected. However, when the second line is added, the line number for the second line is -1 instead of 2. It is also possible to get a line number that is a decimal. I have been told this is intended functionality. The idea is to update the transfer order line number to match the functionality of purchase order line numbers, where the numbers are auto sequenced based on when the line is added using 1, 2, 3, 4, 5...etc

Status Details

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.



Per Lykke Lynnerup

PM, Microsoft

Comments (7)
  • Please resolve this issue as this is creating problem in generating reports reconciliation of inventory and in integrations also.. There is no logic why lines are getting generated in decimals and -ve lines ..this is not functionality but actually a bug which needs to be corrected immediately
  • Need solution its impacting my business.
  • Internal Deliverable reference id : FinOps 169841
  • Creating new lines on a Transfer Order in a sequential order seems logical to me. By making the newly added line the "first" in the transfer order by adding negatives and decimals to line numbers causes confusion within dynamics and integration issues with other systems and tools that use these line numbers. 

    Adding line should be as simple as counting 1, 2, 3. When I add multiple lines after selecting Line 1, decimals quickly add up and adds complexity without benefit to fufillment.  

    Negative and Decimal Line Numbers


    We do not see this issue with Purchase Orders, and do not see the benefit of these odd line numbers for Transfer Orders. 

  • Awesome idea!

  • This makes total sense! Having negative numbers and decimals can cause problems with external 3PL integrations. Unless there is a good reason to allow decimals and negatives, non that i've found, we definitely should change this.

  • This is a good idea!