Install and upgrade

Bitta Commission installs like any other Business Central extension, and installing it prepares each company with safe technical defaults only. This page lists the requirements, walks you through the installation, explains exactly what installation creates and what it does not, and shows you how to check an upgrade with Commission Upgrade Verifications. This guide documents version 1.2.0.0.

Requirements

• Business Central online, version 28.0 or later. Bitta Commission runs on Business Central online only, application and platform version 28.0 or later.
• No other extensions. The app has no dependencies.
• Microsoft AppSource. Bitta Commission 1.2.0.0 is the current version on Microsoft AppSource. Installing it does not start a trial: to get started, request a 30-day trial code.
• The right people. A Business Central administrator who can install extensions installs the app. A user with the Bitta Commission Setup Administrator permission set configures it afterwards. See Permission sets.

Install the extension

Open the Bitta Commission listing on Microsoft AppSource, and follow the steps on the listing to install the app in your Business Central environment. The listing installs the current version, 1.2.0.0. You can also find Bitta Commission in the extension marketplace inside Business Central.

If Bitta Apps supplied a package file for your environment instead, install it with Upload Extension:

1. Search for Extension Management in Tell Me and open it. Choose Manage, then Upload Extension. Select the package file from Bitta Apps, accept the terms and choose Deploy.

2. When the deployment finishes, refresh Extension Management. Bitta Commission by Bitta Apps, LLC is listed as installed.

Then assign the Bitta Commission Setup Administrator permission set to the person who will configure the app, in each company where they work, and activate your trial or subscription on Bitta Commission Setup. See Activate a license.

What installation sets up

Installation runs once in every company that exists when you install. Companies you create later are prepared the same way when they are initialized. In each company, installation:

• Creates the Bitta Commission Setup record with these defaults:

Field	Default
Calculation Precision	0.01
Rounding Direction	Nearest
Closed Period Correction Mode	Block
Retention Period	7Y (seven years)
Background Calculation Enabled	Off
Native Capture Enabled	Off
Native Scanner Ready	Off
Native Scan Batch Size	250
Native Scan Interval (Minutes)	5
Native Notification Maximum Attempts	5
Capture Posting Hints	On
Release Batch Size	100

• Records the installed app version and data schema version, so later upgrades can check them.
• Switches on the core commission engine and creates the switches for the nine optional modules in Commission Feature Management, including AI plan drafting. Each module starts off, unless the company already holds data that only that module creates, for example after a reinstall.
• Registers the upgrade tags, so a later upgrade knows which steps already ran in this company.

Installation creates no plans, participants, calendars, earnings or postings, and because native capture is off, no sales are captured yet. Business defaults, such as the commission number series, a monthly calendar with this year's periods, an immediate eligibility policy and an expense-when-earned accounting policy, are created later by the guided setup or by Prepare Company Defaults on the Bitta Commission Setup Checklist. Existing choices are kept.

When you choose Finish in Set Up Bitta Commission, the guided setup creates your first plan, approves and publishes it, turns native capture and background calculation on, starts the capture and release job queue entries and schedules a daily calculation. See Run the guided setup.

Opening Bitta Commission Setup also re-creates any of these technical defaults that are missing, without changing values you have set.

Upgrade to a newer version

An upgrade keeps your plans, ledgers, settlements, statements and postings and runs once per company:

• The data version is checked first. If the company's data schema version is newer than the app supports, the upgrade stops with "BAA-UPG-PRECONDITION-001 This company's commission data was created by a newer version of Bitta Commission (data version %1) than the version you are installing supports (%2). Going back to an older version isn't supported, so install the newer version instead."
• Each upgrade step runs once. Steps already recorded as upgrade tags are skipped, and missing technical defaults are repaired.
• Modules you already use are switched on. For each module, the upgrade checks whether the company already holds data that only that module creates. Every module in use is switched on, and the Role Center navigation is refreshed. Nothing is switched off.
• A verification row is written for each company after its upgrade step.

Upgrade from 1.1 to 1.2.0.0

An upgrade from version 1.1 keeps all your data. It also prepares the company for the 1.2 changes:

• Release Batch Size on Bitta Commission Setup is set to 100 when the setup row has no value yet.
• Components without line-type exclusions are listed for review. Version 1.2 captures G/L account lines (for example freight and fees), item charge lines and fixed asset lines, which 1.1 did not. A component from 1.1 that has no line-type exclusions would start crediting them, so the upgrade records each such component for review. Plans are never changed automatically, and until you decide, those components keep the 1.1 behaviour and do not credit these lines.
• Commission Season Readiness reports each recorded component as a LINE_TYPE_EXCLUSIONS warning, and Commission Plans and Bitta Commission Setup show a notification with Review components. For each component, choose Add Standard Exclusions (the component must be in a Draft plan version) or Keep Crediting All Lines if it should credit every captured line.
• Setups finished with the earlier wizard count as live. The guided setup does not report them as not running. Plans set up before 1.2 are managed from their own pages.

Check the upgrade verification

Search for Commission Upgrade Verifications in Tell Me. Each row is an immutable, read-only report:

Field	What it tells you
Triggered By	Whether an upgrade (UPGRADE) or a user (MANUAL) started the verification.
Result	Whether every check passed.
Result Code	BAA-UPG-VERIFY-OK, or the first failing check.
Running App Version, Installed App Version	The version that ran the check and the version stored for the company.
Data Schema Version	The stored data schema version.
Upgrade Tags Expected, Upgrade Tags Present	How many upgrade tags this version registers and how many are recorded for the company.
Sampled Entry Count, Hash Mismatch Count	How many ledger entries were hash-sampled and how many failed.
Table Count Hash, Entry Hash	SHA-256 hashes of the table counts and of this row.

Choose Table Counts to see the record counts and hash sampling per table. Choose Run Verification at any time to append a new row. The checks are read-only.

A failed row names the failing check in Result Code: BAA-UPG-VERIFY-DATA-VERSION, BAA-UPG-VERIFY-SCHEMA, BAA-UPG-VERIFY-TAGS, BAA-UPG-VERIFY-HASH or BAA-UPG-VERIFY-COUNT. Keep the row and contact Bitta Apps support. Do not repair commission tables directly.

What's next

Activate your trial or subscription: Activate a license. For what the subscription includes, see Pricing and trial.