Comments
I also need to stress the request to get the Service Management's document line functionalities like Comments to also be in line with what the rest of the ERP solution offers.
It is annoying to constantly bump one's head again lack of vision where the Service Management module differs from care BC functionality and features.
This is a fantastic idea and should be considered by the dev team/product group. I'd love to see this feature for systemusers as well.
We'd like to preserve 'who reported to who' in our system for inactive users, but we don't want to see inactive users who are no longer with the company when viewing our current hierarchy.
It would be a great benefit to our organization if we had the ability to create a true "service-line" purchase order line (line amount only, no quantity and/or unit cost). This is a common feature available in most procurement systems and the current work around in D365 is not ideal as it is confusing to both internal users and our vendors. For reference, the work around is using the quantity field as the amount and setting the unit cost to $1 (ex. 50,000 quantity at $1 unit cost = $50,000).
This work around is used to ensure that a purchase order line may be invoiced multiple times, as opposed to only allowing one invoice if the quantity was set to one. As an example, we may contract for a particular amount (ex. $50,000); however, payment is subject to the statement of work and we may not know how many invoices will be needed for that particular service (hence, unable to define the quantity at the start). A service-line purchase order line would eliminate this issue, eliminate the confusing work around and also improve reporting (as the current work around would not be an accurate representation of quantity ordered).
Please consider voting for this request. Thanks you!
So Important!!
How this is not a a priority one on the fix list is an enigma of its self. But after all feedback to decide to NOT have it in a road map even is amazing and unfortunately speaks volumes but in a non-customer-positive way. It leaves me wondering about if Business central is developed based on customers actual needs on top of financial requirements globally and locally?
If you want business central to never be used by a company that have any customers or suppliers that uses another currency then the local accounting currency- then this is the route to go (small local business only, will need to be charged via partners in LC).
Maybe time to reconsider and add this to short term roadmap?