This is a blocker for ourselves and our clients. Without API's to script in/out custom CDS and API definitions PowerApps is totally unsuitable for change control and quality assurance. The almost total lack of control/auditing possibilities means PowerApps is forever stuck in preview/prototyping.
This and several other blocking suggestions are desperately needed. PowerApps for instance is far from a no-code and low-code solution as soon as we attempt to build real-world apps. It is about time to call it for what it is, "CODE", and put some basic common sense programming support and management support in there like custom functions/macros, reuse, open to change tracing and a proper editor.
Remember PowerApps is made for everyone, and everyone means coding should be made in visual designer (such as macros in Access Web Apps). I hate that i need to learn everday a new whole new technology (now C#) in order to keep running my business database!
Hi @khaledhikmat - I'm happy to say this work is now released and available for updated Common Data Service environments. You can find more details here : https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/overview
For information about this update in geneneral, see : https://powerapps.microsoft.com/en-us/blog/cds-for-apps-march/