Member-only story
I recently tried the Power Apps experiment for creating an application that would display values coming from SQL Server and be able to modify them while keeping the original values visible. It was a refreshing experience outside of the SQL world, albeit very close, that took me back to when I was creating Excel files to meet the needs of my classmates. The feeling of using Power Apps is very close to Excel, and dare I say Access? Microsoft aimed to target a clientele experienced in application creation but also experienced in Excel. In my opinion, although there are some improvements to be made, it is a successful mission!
In the world of data, there’s always been a love-hate relationship with Excel: everyone knows how to use it, and customers can do almost anything with it, but Excel can lead to a lot of errors in the ETL process. Power Apps is the beginning of a solution to this problem: if well built, a Power Apps application allows data to be displayed while allowing it to be modified in a framework intended for this purpose and meeting the needs of the customer. Fantastic!
Of course, Power Apps has its limits, one of the biggest is its limit of 500 records from a data source. However, there is some context: Power Apps is not a data mining tool. That title goes to Power BI. Fortunately, Power Apps and Power BI integrate very well together. You can thus end up…
