Power Bi 1с Коннектор Today

| Method | Technology | Real-time capability | Performance | Complexity | |--------|------------|----------------------|-------------|-------------| | | 1C native HTTP service (OData 2.0/3.0/4.0) | Medium (near real-time) | Medium (paging required) | Low | | 2. Direct SQL | Direct connection to underlying DB (MS SQL, PostgreSQL) | High (live query) | High (but bypasses 1C business logic) | Medium (needs schema understanding) | | 3. Middleware API | REST API (Python/Node.js/Java) reading 1C COM or HTTP services | Medium | Variable (caching possible) | High | 2.1 OData Service (Recommended for Most Cases) 1C provides built-in publication of catalogs, documents, and registers as OData endpoints. Power BI’s OData.Feed connector can consume these.

1C’s Date includes timezone-less datetime. Use DateTimeZone.RemoveZone() in Power Query. 5. Performance Optimization 5.1 Query Folding OData supports partial folding: filters on indexed fields are pushed down. Example: Table.SelectRows(Source, each [Deleted] = false) becomes $filter=Deleted eq false . power bi 1с коннектор

| Name | Method | Price | Key Feature | |------|--------|-------|-------------| | | OData + caching | Commercial | Automatic schema discovery | | Power BI Connector by DevExpress | Direct SQL | Commercial | Supports 1C query language | | OData 1C Free (GitHub) | OData wrapper | Open source | Fixes paging limitations | | Method | Technology | Real-time capability |