Comments
A Sales Credit should have an option to not impact inventory. This would allow properly fixing pricing mistakes, etc. on the original invoice without changing inventory. Sometimes a customer reports a small amount of damage and a simple credit would be much more accurate. G/L accounts will not properly reflect price changes to the correct posted sales invoices and item charges are way too complicated for a simple credit for 1 damaged item. The options should be: Return Inventory or Don't Return Inventory for the Sales Credit memo. A Sales Return should allow you to set an inventory disposition and reason code upon return receipt. A 'return' should not be needed to avoid impacting inventory.
A Sales Credit should have an option to not impact inventory. This would allow properly fixing pricing mistakes, etc. on the original invoice without changing inventory. G/L accounts will not properly reflect price changes to the correct posted sales invoices and item charges are way too complicated for a simple credit for 1 damaged item. The options should be: Return Inventory or Don't Return Inventory for the Sales Credit memo. A Sales Return should allow you to set an inventory disposition and reason code upon return receipt.
As an example - we have around 900 projects created over the last 5 years. Most have the name 'test' or "untitled project" and are therefore redundant. Users have left, but we have no control or visibility of these through an admin portal. Have to create power bi dashboards which hook into the Dataverse directly to generate reports.
This is definitely needed. Our current scenario is where we want to setup a custom channel to manage consent for postal deliveries. Recipients can optin for email and/or postal. The customer then wants to create a mailing list (segment) of everyone who has opted in for post for a specific topic and export the list. This is not possible with Segments as we are unable to identify which channel they are opted in for.