Automates the execution of SQL queries in the Tasy system to load the screen.
Users
46
+1 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#113K
#94K among extensions
Version
1.0.0
updated 15 Apr 2026
Users
monthly, 7 months
Latest, 20 Oct 2026:46 usersMove the mouse over the chart for any month
Ratings count
monthly, 7 months
Latest, 20 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About FindSQL
FindSQL is an essential extension for developers and analysts looking to boost productivity within the Tasy ecosystem. It simplifies debugging and data analysis, allowing you to instantly locate the SELECT statements used to load any page—whether by table name, view ID, or dashboard code.
To function properly, FindSQL requires a complementary API installed on your local environment or server. This API acts as a bridge between the extension and the system logs.
Go to: github.com/davidasteixeira/FindSQL
After installing the extension and the API, follow the steps below to configure the environment:
Access Options: Right-click the extension icon and select Options.
- AppServer Credentials: Enter the AppServer username and password (e.g., usuario.teste).
- Environment URLs: Enter the corresponding addresses for the Dev, QA, and PROD fields.
- Identification: Enter your Tasy system username.
- API Endpoint: The last field is already filled in with the default value; change it only if you customized the port
Save: Click Save to enable the extension on the configured domain.
How to Use
Log in to the Tasy system.
- Click the FindSQL extension icon.
- Enter the table name, view ID, or dashboard code you want to analyze.
- Select the desired database (DEV, QA, or PROD).
- Click Search to view, copy, or download the corresponding SELECT statement.
Technical Note: For optimal performance, ensure that the AppServer is operating correctly and that log generation is properly enabled.