on
RE:
This is a must have and should be a standard config option!
RE:
This should be supported because there are different customer requirement and business context that lead to different behavior for each case of SO.
RE:
This is not a good feature! We should be able to change the datasource without any limitations or restrictions.In my case, I have a Semantic model which is in production. I don't need to do any changes for that one. BUT i want to create some reports in an app. these reports are connected to the production semantic model. I want to be able to use deployment pipelines to push the report AND be able to change connection when needed in that process. Best way is through paramater rules.
RE:
Please let us have this functionality ASAP.
RE:
This a common scenario in business operation; it's necessary to have a function of combining product and service items into 1 Sale Order.
RE:
Basic feature necessary for sales operations involving tangible and non-tangible products and services, definitely a "NEED TO HAVE...not a nice to have" solution.
RE:
Good idea.
RE:
It is common to have a combined invoice (normally customer preference) for multiple Sales order, some with allocation and some without. Allocation needed for some orders due to contribution from different BUs. This should be a standard feature.
RE:
Single SO Invoice reduce processing time and increase productivity, achieving GEPO.
RE:
it will improve efficiency, reduce manual revenue allocation errors and prevent manipulation of invoices for fraudulent transaction.