@blinabj
Ok, I will explain why I will never use it as my DataSource, even for micro projects. I hope this helps others to make better decisions when planning new apps.
1. Way how Power Apps interact with the file, If Excel File is open, it will go into Lock mode Power Apps will not be able to create or Update any records. So if a group of people are working on it for some reason and forget to close it, **bleep**, what a pain.
Not only that, if you would like to manipulate data by using Power Automate, sadly Power Automate, after Modification putting the Excel file in Lock mode for 6 min means Power Apps will again connect to it and can't do any operations.
2. Power Apps in a moment when You first time connecting to the file creating a column called _PowerAppsID_ and creating a really long ID for each record in the table. Now it's very buggy, and if you play too much with the table, the only way to fix it is to create a new File, create a new table and re-connect it to Power Apps again.
3.Power Apps on the first connection decide what the type of column in your Table will be, and my gosh, this can surprise you a lot when most of Number types become Text and Date become something else and then even if you change them, power apps will ignore the changes till you run the process of reconnecting of the connector again keep in mind that will not give you 100% result as well 🙂
4. DateTime iso8601 Power Automate hates it so do PowerApps in some scenarios, as both use UTC
5. Delegations nearly not existing
Sharepoint is easy to learn and has so much to give for a free Data Source. The time you spend on frustrating and debugging Excel connectors will be twice or more longer than just checking some YouTube video on how to set up SharePoint sites and Lists to drive Power Apps from them.
