Version 2021.10.14.1

Change to versioning

  • We have switched to date based versioning so you can better understand how recent your version of Loome Publish is.


Custom Assets source system

We have a new type of source system, the Custom Assets source system. The Custom Assets source system creates a database in SQL Server and then syncs content from this database every 10 minutes.

You can create your own asset types in Loome Publish and then write your own code to populate this database from line of business applications or products that we don’t have available as first party source systems.

You can optionally also write your own embedding libraries for your custom asset types to get a complete integration experience. We will be providing a complete guide to accomplishing this in the near future.

Service Principal support when syncing content from Power BI

You can now use a service principal to sync content from Power BI in to Loome Publish.

If you are hosting Loome Publish on-premises, you can enter a Service Principal Client ID and Secret directly via the user interface.

If you are hosting Loome Publish in Azure, you have the option to configure your Azure App Service as a Managed System Identity and then retrieve either a secret or a certificate for the Service Principal from an Azure Key Vault for added security.

Please note that due to limitations implemented by Microsoft, you can only use Service Principals to sync workspace content. Options for app content syncing will be disabled on the source system configuration screen when you select to use a Service Principal.

You can find more information on how to configure a Service Principal for use with Power BI here -

Support Graph API for outgoing email

As Microsoft are deprecating SMTP usage on Office 365, we have added the ability to send outgoing email via Microsoft Graph API.

If you are hosting Loome Publish on-premises, you can enter a username, password, and Azure AD Application Registration to allow you to send email via Microsoft Graph API.

If you are hosting Loome Publish in Azure, you have the option to configure your Azure App Service as a Managed System Identity and then retrieve the username and password from Azure Key Vault for added security.

In order to make use of this feature, you will need to configure an Azure AD Application Registration with delegated permissions to Microsoft Graph for the Mail.Send permission and Allow public client flows enabled. This can be done to your existing Azure AD Application Registration, or you can create a new Azure AD Application Registration.

Support Managed Identities for Loome Publish database access

If you are hosting Loome Publish in Azure, you now have the ability to use a Managed System Identity to provide access from the Loome Publish Azure App Service to the Loome Publish Azure SQL DB. Simply configure your Azure App Service with a Managed System Identity and provide it access to the Azure SQL DB. Once completed, re-run the Loome Publish installer, removing the user id and password from the connection string, and adding Authentication=Active Directory Default; to the connection string.

You can find out more information here on how to configure a Managed System Identity and provide it access to an Azure SQL DB here -

Rework of the asset registration wizard

The asset registration wizard has not been reworked to allow you to optionally publish an asset directly from the wizard. Each step will allow you to either register the asset, or publish the asset where enough information has been provided to do so.

Rework of logging framework

The logging framework has been reworked to provide a better experience for administrators. All logging is now done to file under the /logs folder of the application. Logging is enabled by default now and set at the error level. With this in mind you can wire up your logging systems to retrieve and alert on any issues logged by Loome Publish.

To collect more detailed logs you can edit the web.config of the application and change the serilog:minimum-level app key to either Information or Debug.

Logs create one file per day that is date stamped, files are removed after 30 days.


  • Keep filtering state when browsing to and from an asset on an asset board.
  • Improved the layout of the drafts area button on the drafts page.
  • Updated the default tile layouts on a new installation of Loome Publish to be more appealing.
  • Term sets can be hidden from the left hand navigation from the metadata management page.
  • Added Loome Publish URL to outgoing emails.
  • Added Azure SQL Execution strategy for Loome Publish instances hosted on an Azure SQL DB, this should ensure a robust connection between the Azure App Service and the DB.
  • Removed BiPortalDb_DatabasePublish connection string from application as it is no longer required.
  • Added a swagger endpoint for Loome Publish API.
  • Added ability to specify a default landing page for users.
  • Updated a number of third party libraries to improve security.
  • Added the ability to specify the how the left hand navigation menu works by default. For example you can choose to have the left hand menu always expanded.
  • You can configure a source system to remove assets in Loome Publish where they no longer exist in the source system. This is the default action for new source systems.
  • Made asset titles on asset cards in to hyperlinks so users can click through to an asset through the title.


  • Fixed a bug where the asset registration wizard would not allow you to proceed to the drafts area.
  • Fixed a bug where sharing a link with a user via email would take them to the home page if they were required to sign in.
  • Fixed a bug with editing custom attributes on an asset.
  • Fixed a bug where you would be prompted to select assets while bulk editing assets, despite having already selected assets.
  • Fixed a bug that prevented strict CSP policies from being applied to IIS application or app service.
  • Fixed a bug with usage information that may prevent asset cards from loading on an asset board.
  • Fixed a bug where a source system could be saved without entering a password or secret.
  • Fixed a SQL injection vulnerability.
  • Fixed an XSS vulnerability.
  • Fixed an issue where custom attributes were validating before hitting next/submit/save.
  • Fixed an issue where editing an item in the app navigation panel caused a new item to be created.
  • Fixed a bug where tiles with no title caused a failure in the Power BI source system.
  • Fixed an issue where Power BI embedding token would not be refreshed after an hour of leaving a Power BI report idle on screen.
  • Fixed issues with the external OData endpoints for the data catalogue.
  • Fixed an issue that allowed required custom attributes to be saved without entering a value.
  • Fixed an issue where you could not order the interactions on the usage detail table.