Release notes of Fiedler Data Tools

Fiedler Data Import and Fiedler Data Export share one version number. A version always ships both apps, their command line clients and their automation scripts for Manage, and one licence covers all of it. This page lists every version, the newest first, with what it changed and what an upgrade needs.

To install a version, follow the installation guide. Its section 16 shows how an update works in general. The notes below add what each version needs on top of that.

The versions

#

Version 1.0.0 ran on our own systems only. Its images and its kit are not public, so a new installation starts with the newest version.

Which version runs. Each app’s administration screen shows its version and build. The command line shows it too:

curl -s https://<host><path>/api/version

The answer is JSON with appVersion and buildId.

The images of each version are on quay.io under the version’s tag. Refer to them by digest, as the installation guide shows. The digests:

The full digests are in the README.md of each kit. skopeo inspect prints them as well, and cosign verify checks a signed one.

1.0.2

#

The first signed release, with the fixes from our first installation as a customer would do it.

• Signed images. cosign signs every image, and each app image carries its SBOM as a CycloneDX attestation. The public key is in the installation guide and on each image’s quay.io page.
• Export through an object structure. Manage reads an object structure through its REST API only when the structure’s Consumed By is in the system property mxe.oslc.validusewith. An export through such a structure, for example DMCURRENCY, failed at the plan with BMXAA1283E. The export now offers only the structures Manage reads, and names the reason when a plan asks for another one. A failed plan or run writes Manage’s own message into the job log, and the audit record of a failed plan names the object structure it asked for.
• Row 3 of an export holds the attribute descriptions, in the language of row 1 where Manage has a translation. The sample row is gone. Row 2 is bold.
• Sessions follow MAS. Both apps keep MAS’s idle timeout, with its countdown. They follow a logout from MAS within seconds, and an administrator’s forced logout as well.
• The administration screens name the rights a first installation needs: the applications AUTOSCRIPT and DESIGNER, and the object structure MXAPIAUTOSCRIPT. “My options” lists the object structures. After an install or a profile refresh, the screen waits for the new rights to arrive, and an install report says “pending” until they do.
• A sign-in that cannot finish now says why, for example after the back button or a second sign-in in another tab, and offers “Sign in again”. The reason goes to the log. When the administration cannot be read for a reason other than missing rights, the screen shows the server’s message.
• Importer fixes, scripts 0.5.14. A status of type ALN keeps its case, so an automation script saves as Active. Under a new record whose children Manage created itself, a child row with a key of its own fills the matching child. A sign-in that Manage refuses, for example under admin mode, counts as not sent, so no row is left in doubt, and the job names Manage’s message.
• Links and addresses. Support and questions go to support@fiedler-it.at, licences to sales@fiedler-it.at. Support runs from 9:00 to 16:00, Vienna time. The export’s hint on a query links our article on the oslc.where clause.

Upgrade from 1.0.1. Install the new images as usual. The licence agreement has a new version, so an administrator accepts it again on the administration screen. Then choose Install again on both administration screens, because the scripts in Manage change.

1.0.1

#

The first release on a public registry. Anyone can pull the images from quay.io, and they contain no readable source code.

• Obfuscated code. Each server runs from one obfuscated file, and the command line clients are built from one. The automation scripts that the apps install in Manage are obfuscated too. The screens are minified. Third-party packages stay as their makers ship them, with their licence texts.
• Image labels. Each image names its title, version, commit, maker, licence and product page in the standard OCI labels.
• Source offer. The third-party notices of each image offer the source of the base image’s GPL and LGPL packages.
• Security update. body-parser 1.20.9, which express uses, fixes CVE-2026-111181: a broken compressed request body could stop the server.

Upgrade from 1.0.0. Install the new images as usual. The apps behave as before. The scripts keep their versions, so the administration screen reports them up to date. To get the obfuscated scripts into Manage, choose Install again on both administration screens.

Supported: IBM Maximo Application Suite 9.1 and later. We tested 1.0.1 on MAS 9.2.7 with Manage 9.2.4: the importer’s examples suite and the export’s round-trip suite passed with the obfuscated images and scripts.

1.0.0

#

The first release of Fiedler Data Import and Fiedler Data Export.

The automation scripts have version numbers of their own. The administration screen of each app compares the scripts in the app with the scripts in Manage, and installs them with one button.

Fiedler Data Import reads Excel workbooks and writes their records into Manage, as the user who signed in, with that user’s rights.

• Excel workbooks. The import reads .xlsx workbooks: simple and extended sheets, specification sheets, multilevel hierarchies, INDEX sheets, texts in more languages, long descriptions, key changes, and control columns such as $DELETE, $ADDONLY and $UPDATEONLY.
• A plan before every run. The plan shows per row what the run will do: insert, update, unchanged, skip or error. Manage stays as it is until the user starts the run.
• Two ways to write. The business object path runs Manage’s business rules and the customer’s automation scripts. The object structure path writes through a Manage object structure.
• Results. A result workbook marks every row in colour and writes back the keys Manage gave. A stopped job resumes where it stopped, and failed rows can be reviewed and sent again.
• Settings in four layers: the ConfigMap, a configuration script in Manage, the workbook’s CONFIG sheet and the job’s options. Five callback points call the customer’s automation scripts during a job.
• For administrators: an administration screen that installs and removes the Manage side, a job queue, retention and purge, an audit record per job, an import report, Prometheus metrics with eight alerts, a Grafana dashboard, and backup and restore scripts for the data volume.
• The command line client fdi does what the screens do, signs in with the browser or an API key, and runs test suites of workbooks against a test system.

Fiedler Data Export reads records from Manage, as the user who signed in, and writes them into workbooks of the same format. A workbook it writes imports through Fiedler Data Import as it is.

• Layouts decide the sheets and the columns: Records, Transfer, With children, a saved layout, or the header rows of any workbook. Saved layouts can be shared with security groups, and Excel is the column editor.
• Two ways to read: the business object path reads every attribute and relationship, and the object structure path reads through a Manage object structure.
• Row 1 in the user’s language. A generated layout writes its titles in the language of the user who exports. Row 2, the attribute names, stays the same in every language.
• Large exports split their files, so that Fiedler Data Import can read each file.
• For administrators: an administration screen that installs and removes the Manage side, retention, an audit record per job, a nightly export as a Kubernetes CronJob, Prometheus metrics with six alerts, and a Grafana dashboard.
• The command line client fde plans and runs exports, manages layouts, and runs the round-trip suite.

Editions. Both apps run without a licence in the free edition. It imports up to 200 rows of each sheet and exports up to 200 records, and up to three users may use each app. The command line clients and scheduled exports need a licence. A licence lifts the row limits and names how many users may use each app.

Behaviour to know. These still hold in every later version:

• The apps read .xlsx workbooks. Save an old .xls workbook as .xlsx in Excel first.
• The importer never calculates a formula. It reads the value that Excel stored with the formula. A formula cell without a stored value is an error; save the workbook in Excel to fix it.
• The screens are in English.
• On the object structure path, Manage sets the date of a status change itself and ignores the workbook’s STATUSDATE. The plan shows a warning on such a row. The business object path takes the workbook’s date.
• An upgrade stops the app’s pod before the new pod starts, because one pod holds the data volume. A job that was running waits for its owner, who resumes it.
• A callback script that changes data on its own can run twice for a row group that a resume sends again.
• On the export, a specification attribute with rows in several sections exports its first row. The record carries the issue read.specManyRows.
• The export splits its files at Fiedler Data Import’s default read limits: 1 GiB of XML and 50 million cells per workbook.

Known issues of 1.0.0 to 1.0.2. All three images contain qs 6.15.3, which has two advisories of medium severity, CVE-2026-82417 and CVE-2026-82562. qs comes in with express, and the next version brings 6.16.0, which fixes both.

Help

#

Write to support@fiedler-it.at with the app, its version and build from the administration screen, and what you saw. For a licence, a trial or a price, get in touch.

IBM and Maximo are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.