Power Bi 1с Коннектор Upd May 2026

| 1C Type | Power BI Type | Notes | |---------|---------------|-------| | String | Text | | | Number (decimal) | Decimal | Watch for scale (max 28 digits) | | Number (integer) | Whole number | | | Date | Date/Time | | | Boolean | True/False | | | UUID (GUID) | Text | Convert to string | | Link (ref to object) | Text or Record | Expand to key field | | Tabular section | Table (nested) | Unpivot or expand |

SELECT Sales.Ref AS SaleID, Sales.Date, Products.Name AS ProductName, Sales.Quantity FROM Document.Sales AS Sales LEFT JOIN Catalog.Products AS Products ON Sales.Product = Products.Ref WHERE Sales.Date >= DATETIME(2024,1,1) Publish this as an OData data source.

let BaseUrl = "http://1c-server/odata/standard/odata/Catalog_Products", GetPage = (url) => let Response = OData.Feed(url, null, [Implementation="2.0"]), NextLink = if Record.HasFields(Response, "odata.nextLink") then Response[odata.nextLink] else null in Response, AllPages = List.Generate( () => [Page = GetPage(BaseUrl), Next = null], each [Page] <> null, each [Page = GetPage([Next]), Next = null], each [Page] ), Combined = Table.Combine(AllPages) in Combined power bi 1с коннектор

OData connector with incremental refresh.

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: | 1C Type | Power BI Type |

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 .

| 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 | Use NextLink handling – Power Query automatically manages

| 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.