Skip to main content

Updates

New versions of the Datafeed App are released from time to time to add features, improve reliability, and keep pace with new fields added to the Kiss data service.

Checking your current version​

Open the Kiss Datafeed Configuration tool and select About from the left-hand navigation rail. You'll see:

  • The installed version of the app.
  • The active API profile the app is built for.
  • The server API version most recently reported by Kiss.

If the server API version is ahead of the version your app supports, an amber triangle appears next to the value. This is a hint that a newer installer is available.

How updates are delivered​

Updates are published as a new installer (e.g. KissDatafeedSetup-1.1.0.exe) on the Kiss customer portal. Your account manager will let you know when a new version is available, and you can download it from the same place you got the original installer.

Installing a new version​

Updating is the same as installing for the first time:

  1. Download the new installer from the customer portal.
  2. Double-click it on the machine that runs the Datafeed App.
  3. Accept the User Account Control prompt.
  4. Walk through the wizard accepting every default.
  5. Click Finish.

Behind the scenes the installer:

  • Stops the running background service.
  • Removes the previous version's program files.
  • Installs the new version.
  • Re-registers and re-starts the service.

Your configuration, credentials, state, and logs are preserved. After the upgrade, the app picks up where it left off and your next scheduled sync runs as normal.

When you should update​

You don't need to update immediately every time a new version is released. Sensible triggers are:

  • An amber triangle on the About screen — Kiss has released new features that your version doesn't see.
  • A known issue in your current version that's fixed in a newer release.
  • Routine refresh — once or twice a year is a healthy cadence.

Verifying the installer​

Always download installers from the official Kiss customer portal, and keep the downloaded .exe until you have completed the install. If you ever need to confirm that a file you have is the one Kiss published, your account manager can supply a SHA-256 checksum on request — running Get-FileHash in PowerShell against your local copy should produce the same value.

Future releases will be code-signed; when that happens the publisher Kiss Costumes will appear under Properties → Digital Signatures on the installer file. Until that change ships, treat the customer portal as the source of truth for installer provenance.

Rolling back​

If a new version causes a problem in your environment, you can roll back to a previous version by running the previous installer. Because configuration and credentials are preserved on disk between installs, the old version will pick up your existing setup.

We recommend contacting support before rolling back so that we can investigate the underlying problem and prevent it from affecting other customers.