let Source = OData.Feed( "http://1c-server/1c/odata/standard/odata/Catalog_Products", null, [Implementation="2.0", Timeout=#duration(0,10,0,0)] ), #"Expanded Properties" = Table.ExpandRecordColumn(Source, "MainProperties", ...) in #"Expanded Properties" 1C returns data in chunks. Use NextLink handling – Power Query automatically manages this with [Implementation="2.0"] . For better performance, add $top=5000 and iterate. 3.4 Authentication Supported methods: Basic, Windows (NTLM/Kerberos), Anonymous. For Power BI Service, use On-premises data gateway with Windows authentication. 4. Data Type Mapping 1C data types and their Power BI equivalents:
| 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 | power bi 1с коннектор
| 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. let Source = OData