Power BI on Top of Priority and Hashavshevet: Connecting the Data and Keeping It Fresh

To get Priority ERP data into Power BI there are two documented routes: the Priority REST API, an OData service that Power BI's OData Feed connector reads, and the Priority ODBC driver, which exposes Priority forms as SQL tables. Hashavshevet on the desktop usually means scheduled exports or read-only database access, and WizCloud exports data only through reports you design first.

This guide is for controllers, finance managers and developers who already know they want Power BI and need to know what it takes on the Israeli ERP side. The broader architecture question - whether to point BI straight at the systems or stage the data first - is covered in connecting CRM and ERP to a BI dashboard. Here the focus is the specific connectors, licenses and limits.

Which route fits your Priority installation?

Three facts about your installation decide the route: whether Priority runs in the cloud or on your own server, which modules you license, and how many rows each report really needs.

If the ODBC module is already licensed, it is usually the simpler route for large tables, because Power BI's ODBC connector accepts a SQL statement. The REST API is the route when ODBC is not licensed or when the same API user already serves other integrations.

Reading the Priority REST API as an OData feed

The Priority REST API is based on the Open Data Protocol, so Power BI's OData Feed connector can read it without custom code. The service root has the shape https://<server>/odata/Priority/<tabula.ini>/<environment>, where the environment is the company's internal name, not its display name. A Priority system administrator can output the exact root with the Send Program Activation Link program. The traps in that URL are covered in the Priority REST API errors that waste the most time.

• Point each query at one form, such as ORDERS or LOGPART, never at the service root, and narrow it with $filter. Priority's own example is LOGPART?$filter=FAMILYNAME eq '001'.
• Page large forms with $top and $skip, which Priority documents for exactly this.
• Read $metadata first. Customised forms and fields differ between installations, so field names from another company's report will not match yours.
• Select Skip Test Connection when you set up refresh in the Power BI service for a URL that carries query options. Microsoft's connector documentation explains that the service tests credentials while ignoring those options.
• Choose the authentication before you build. Basic uses an active Priority user with an API license, personal access tokens exist from version 19.1, and OAuth2 needs the External ID module. Basic stops working once External ID is enabled.

On Priority Cloud the API is throttled per tenant: 100 calls per minute per user, up to 10 requests processed at once with 5 more queued, and any request that runs longer than 3 minutes is dropped. Throttled calls receive HTTP 429. A refresh that walks a dozen large forms in small pages reaches those numbers quickly, which is the practical reason to filter every query to the date range the report shows.

Priority counts an API transaction when a record is added or updated, and transactions are bought in packages of 10,000 a month. A report that only reads should not consume them, yet Priority's own example assigns transactions to a Power BI user, so confirm with your Priority partner how your license report counts it.

The Priority ODBC driver: forms as SQL tables

The Priority ODBC driver lets a third-party tool query Priority with SQL. It does not open the underlying MSSQL or Oracle database; it presents the same data the forms show in the interface, one table per form.

• Each Priority company is a separate database named after its internal company name, so reporting on two companies means two connections.
• A subform is addressed through its parent, for example ORDERS_sep_ORDERITEMS. Querying ORDERITEMS alone returns an error.
• Only forms listed in the Define ODBC Forms form are exposed, and the connecting user sees only what that user can see in the interface.
• Results are capped by the MAXFORMLINES system constant, 10,000 by default. Priority recommends paging rather than raising the cap.
• On a local installation the driver needs the BIN95 folder from version 22.1.21 onward and a reinstalled application server; cloud customers skip those steps.

Because the ODBC connection is configured in the Windows ODBC Data Source Administrator, scheduled refresh in the Power BI service runs through an on-premises data gateway installed on a machine that has the driver.

What are the options for Hashavshevet and WizCloud?

Hashavshevet on the desktop has no single API answer: what exists depends on the version, the edition and how it was installed, which is why the questions in what to establish before automating Hashavshevet come before any estimate. For reporting, two routes usually work: a scheduled export that you process as raw text, and direct reads from the database with a dedicated read-only user. Writes to the accounting database are never part of a BI project.

WizCloud, the cloud Hashavshevet, is different. Its ExportDataApi/exportData endpoint does not accept a query; it runs a report you first design in the WizCloud report generator, exported with the External option. Authentication goes through createSession, which returns a wizAuthToken valid for 24 hours. The details are in exporting reports from WizCloud through the API.

That two-step flow fits Power BI poorly. Microsoft notes that the service generally cannot refresh a dynamic data source whose connection details are computed while the query runs, with narrow exceptions such as the RelativePath and Query options of Web.Contents. The pattern that holds up is a small scheduled job that calls exportData, treats Data not found as an empty day rather than a failure, and writes the rows to a database or file that Power BI reads.

How often can Power BI refresh, and when is a gateway required?

A semantic model in a Pro workspace (shared capacity) is limited to 8 scheduled refreshes a day. On Premium capacity, Premium Per User or Fabric capacity the limit is 48. As of September 2026, Microsoft's US pricing page lists Power BI Pro at $14 and Premium Per User at $24 per user per month, paid yearly.

• The daily quota resets at 12:01 AM in the time zone chosen on the semantic model settings page, so set it to Israel time before placing the slots.
• The service aims to start a refresh within 15 minutes of its slot, and the start can slip by up to an hour when resources are short.
• Scheduled refresh is paused after two months in which nobody opened a report built on the model.
• A semantic model uses a single gateway connection. When one query merges an on-premises source with a cloud source, the cloud source is also read through the gateway.

The on-premises data gateway comes in standard mode, for shared connections and gateway clusters, and personal mode, for one user refreshing their own models. For a company report built on Priority or Hashavshevet, standard mode on a server that stays on is the one that survives a staff change.

Hebrew and right-to-left in the report

The Power BI service runs in Hebrew, but Power BI Desktop is available in the same languages except Hebrew and Arabic, and Desktop does not support right-to-left languages. Inside reports, the layout of visuals does not change for a right-to-left language such as Hebrew. In practice you build the right-to-left reading order yourself: slicers and the first key figure on the right, and tables whose first column is the one a Hebrew reader looks at first. Check Hebrew text fields from Priority, such as item descriptions, in the actual visuals before you publish.

What goes wrong, and how you find out

• A report starts failing with HTTP 429 after new pages are added, because the refresh now crosses Priority Cloud's per-minute limit.
• An ODBC table silently stops at 10,000 rows, which surfaces as totals that are too low rather than as an error.
• A WizCloud report is edited in the interface and the stored export starts returning Params not found or not match.
• Nobody opens the report during a quiet period, scheduled refresh pauses, and the owner's notification email goes unread.

Sources

• Priority Developer Portal - REST API: service root, fair use policy, transaction counting
• Priority Developer Portal - ODBC driver: requirements, schema, MAXFORMLINES
• Microsoft Learn - Data refresh in Power BI: 8 and 48 daily refreshes, gateways, dynamic data sources