Power Platform Community Forum Thread Details

I'm building a PowerApps application with the following requirements:

The app has multiple filters for users to select from.
Each unique combination of filter selections corresponds to a specific SQL table.
There are 240 possible filter combinations, thus 240 different SQL tables that might need to be queried.
When a user selects a combination of filters, I need to fetch the content of the corresponding SQL table and display the results in the PowerApps site.
The queries will be simple SELECT statements to show the content of the tables. No complex queries or joins are involved.
The SQL tables are in SQL Server .The number of records in each table varies but can be substantial. The app needs to be able to handle concurrent users making different filter selections. All queries will be simple SELECT statements to retrieve table contents. No complex operations, joins, or data manipulations are required.

I've seen some examples that use Power Automate for similar scenarios. However, I'm unsure if there are any limitations to this approach, especially considering the large number of potential tables to query.

What's the most efficient way to handle this many potential SQL queries in PowerApps, given that they're all simple SELECT statements?
Are there any limitations or performance concerns I should be awarree of when dealing with 240 potential tables, even with simple queries.
Is using Power Automate the best approach, or are there other solutions within PowerApps that might be more suitable for these straightforward SELECT queries? How can I ensure that the app remains responsive and user-friendly while handling these queries?

Any advice or alternative approach?

Categories:

Building Power Apps