Release notes August 2026

Ecoinvent can now be selected as a preferred dataset for mapping emission factors in your Inventory and Imports; Moving activities between activity categories is now much easier — move to any category, regardless of the source.

What's new?

Ecoinvent as a preferred dataset

Ecoinvent can now be selected as a preferred dataset under Boundaries > Emission Factors.

Once selected, you will now be able to:

  • Choose Ecoinvent emission factors using the keyword and detail dropdowns in the Inventory
  • Map to Ecoinvent emission factors using keyword and detail during imports

Please note: due to the size of the Ecoinvent dataset, it has no import template for keyword and detail factor mapping.

Easier moves between activity categories

Moving activities between activity categories is now significantly simpler.

Previously, moving an item required first selecting both the original activity category and the destination activity category before the move could be completed. Now, you can move items to any activity category, regardless of which activity categories are currently shown in the inventory — no need to match or pre-select the source category first.

Additional work on the code base

In addition to the two features above, this release includes under-the-hood improvements: enhanced login security aligned with current best practices, and infrastructure groundwork that will power upcoming import features like batch AI imports.

Minor updates & fixes

Fixes

  • Fixed a case where Request creations could fail
  • Fixed decimail point and thousand separator inconsistencies in dual reporting lines
  • Improvements to AI Imports for certain invoice types
  • Fixed a case where a fifth level could be created in Organizational Units which caused issues when generating reports
  • Fixed UX bug where name of Expert User changed to Admin would not appear in confirmation dialog
  • Many more minor fixes

API Updates

What's New

None

What’s Deleted

None

What's Deprecated

None

What's Changed

  • PUT /organizational-units/v1/organizational-units/{organizational_unit_id}
  • POST /organizational-units/v1/organizational-units
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.