Release Notes 2025.5.0 – FireStart Help

Improved user search behaviour when trying to add or update a user field in SharePoint. It should now be possible to add/update a user field with either Name, LoginName, Email, UPN (UserPrincipalName) regardless of the configured SharePoint display property.

Resolved an issue that caused taxonomy fields to be resolved incorrectly.
Resolved an issue that caused some system fields in rare cases to be empty and not correctly fetched.
Resolved an issue that caused events not being resolved correctly for User or Lookup SharePoint Online fields.

Resolved an issue that would cause an exception when trying to load all data of a SharePoint list when a user was no longer found in SharePoint.
Resolved an issue caused by the previously added DB-Migration that would write values in the wrong format. These values have been corrected into the correct format and should be able to be used by the system without issues.

Added an import migration which affects exports exported in versions before or with 2025.5.0. This migration, similar to the previous DB-migrations, migrates any SharePointOnline-Activity connections to use the new OAuth- instead of Basic-Authentication.
Improved SharePoint Online data fetching preventing ‘429-too many request' responses
Resolved an issue that would cause an exception in rare cases when trying to write a user value to a SharePoint field of type 'user'.
Resolved an issue which caused data filters and item selections to return an empty list when using a field of type ‘boolean’ (SharePoint Yes/No-Field) and not using the AdapterItemCache. Those filters should work correctly now.

Added DB-Migration that migrates very rare cases where running workflows still have Actions using the old Basic authentication causing issues when executing the SharePoint Activity.

Sql migration scripts optimizations: Faster database upgrade for installations with many SharePoint Online workflow activities.

Added an additional layer to better detect Taxonomy terms from term stores. Now the parent terms will be respected correctly.
Added support for additional (dependent) lookup fields.

Resolve an issue that caused an error when trying to update a Taxonomy (ManagedMetadata) field.
Resolved an issue that caused an error in rare cases when trying to update a User field with a certain Lookup field type.
Resolved an issue when trying to set permissions to a group. Now the reason is correctly shown (either no match or too many matches) and the group search now also correctly finds the given group.
Resolved an issue that prevented the use of BEs as connection for the SetPermission Activity.
Version comments are now correctly written when configured in the MoveFile Activity.
Resolved an issue that caused wrong behaviour if SharePoint Online user fields were written. This issue was caused by case sensitivity and was resolved.
Resolved an issue that would wrongly return the first user present in the siteusers collection when no user was found.
Fixed an issue that caused a CORS error. For now to prevent the issue, all origins are allowed. This will be fixed and improved in a future release.

Resolved an issue when a BE mapping was created with only readonly fields causing events to trigger an exception.
Resolved an issue that caused an error when trying to get a user Email using the SP-GetUserInformation Activity.
Resolved an issue that would prevent uploading new files to a Document Library
Resolved an issue that caused 429 error when lists contained lots of deleted user objects.

Resolved an issue that caused the Move File activity to fail when moving a file into a SharePoint list instead of a document library. The file is now correctly added as an attachment to the list item.
Resolved an issue that caused the Set Permission activity to report no match for a user that actually exists. Users are now correctly resolved by Name, LoginName, Email, email alias or UPN (UserPrincipalName) — previously a user referenced by an alias or a non-primary email address could be reported as not found.
Resolved an issue that caused the Set Permission activity to fail with an unexpected error when the specified user or group could not be resolved.

Resolved an issue that caused user fields not being filled after receiving events in some cases.
Resolved an issue that caused the additional lookup field ‘ID’ not having a values after fetching all SharePoint data.
Resolved an issue that caused the Outlook AddIn not being uninstallable anymore. Future installations are working as intended again. If you encounter an issue when unintalling the FireStart Outlook AddIn please reach out to support@firestart.com.
Resolved an issue that caused an exception when trying to upload files with special characters to a SharePoint DocumentLibrary.
Added alphabetical ordering to SharePoint Online list of lists when creating a new Business Entity mapping again.

Improvements

Added logic that handles a SharePoint REST Api internal limitation of only being able to have 12 lookup-able fields (lookup or user fields) in a single query. It is now possible to have as many of those fields in a single BE mapping.

BugFixes

Resolved an issue that caused some lookup display fields to not have a value after fetching data from SharePoint.
Resolved an issue that caused user fields to display the raw JSON data when the column name started with a special character.
Resolved an issue that caused ExchangeMailWatcher from still applying the ‘read’ state to mails even though their process was already undeployed. → This could be caused when there was an error during the deploy process or when undeploying models using database statements.
Resolved an issue that resulted in a ’user not found'-error when a SharePoint user search was triggered (e.g. by trying to write a user to a user field) and the search value had trailing white spaces.