[FEATURE REQUEST] SQLite Connector for PowerApps

Type of Connector

Certified Connector

Name of Connector

SQLite

Is your feature request related to a problem? Please describe.

The absence of a native SQLite connector in PowerApps creates several challenges and inefficiencies for developers and businesses, particularly for those relying on SQLite for lightweight and local database solutions. The lack of a SQLite connector contradicts the core principles of PowerApps: accessibility, simplicity, and low-code development. Developers face unnecessary hurdles to integrate SQLite, which limits PowerApps' adoption and hinders innovation, especially for small-scale or offline-first applications.

Describe the solution you'd like

I would like to request the addition of a SQLite connector to PowerApps. SQLite is a widely-used, lightweight, and self-contained database engine, popular for its simplicity and efficiency. Integrating a native SQLite connector in PowerApps would greatly enhance its usability for many developers and organizations relying on SQLite for data storage.

Proposed Features

A native SQLite connector could include:

• Read/Write Support: Allow CRUD operations (Create, Read, Update, Delete) on SQLite databases.

• Schema Support: Enable PowerApps to fetch SQLite table schemas for dynamic app generation.

• Local File Integration: Support SQLite databases stored locally on devices or accessible via a network path.

• Connection Settings:

  • File path or URI to the SQLite database file.
  • Password protection support for encrypted SQLite files.

• Offline Mode Compatibility: Enable PowerApps to leverage SQLite for offline functionality.

Describe alternatives you've considered

One of the most common alternatives is creating a Custom API that acts as an intermediary between PowerApps and SQLite. This allows PowerApps to interact with the SQLite database via HTTP requests.

Additional context

N/A

No files, tests, or entry points are named. Start by reviewing the repository's existing connector structure and compare the requested CRUD, schema, local-file, encryption, and offline capabilities against it; done would require a scoped, maintainable SQLite connector rather than the broad request alone.