Comments
Certain organizations will not approve Microsoft Teams as a secure and viable solution. Currently the only alternative for members of those organizations is to @mention a huge number of users in every single post (including all replies) they make. It ultimately dissuades users from embracing Dynamics as a solution because generic e-mails remain significantly more efficient for larger teams. This is a bigger enabler than the votes indicate.
This is especially important since we are urged to break up monolithic apps into smaller ones. Imagine having apps neatly broken up, ending up with two apps A and B, and one for the interplay (such as adding a B field to an A table) that is depending on them both: AB. Now if you're exposing the data of these apps via APIs, and you want to support A and B to be used both independently (which is the idea of having them separated) and combined (with the AB app on top of them), you would need API pages for A tables and for B tables, but as soon as you want to expose the B field that is added to the A table, you would also need to create an exact copy of the API page for the A table with just one B field added to it. That doesn't make sense.
If only we could
- add new fields to an API page, or
- allow extensions with the same prefix to extend API pages, or
- in some other way allow another extension to extend an API page
You could also extend the Status to say
Backorder - when sales order has incomplete lines
Shipped - when sales order is shipped but not invoiced
Cancelled - when the customer wishes to cancel the remaining quantities
ProductionPlanned - when some items are in planning
NotPlanned - when some items are not yet planned
Just some ideas to help filter sales order status