Click on any published known bug listed below to view a detailed description, including the issue's specifics, potential workarounds, and the planned version for its resolution.
Description
The problem is related to a recent change introduced by Microsoft in the March update of Microsoft 365, which is currently being rolled out to users on the Microsoft 365 Current Channel.
Workaround
If you are affected by this issue, you can resolve it by downloading and installing WorkPoint Express Hotfix 6.11.1 (64bit Office edition).
Important: This hotfix should only be installed if you are specifically experiencing the described issue. We recommend installing the hotfix on a single PC first to verify that it resolves the issue, before proceeding with a wider deployment.
Status
Known bug. The issue does not affect users on the Enterprise Channel.
Description
When a user without Site Collection Administrator permissions (e.g., standard end users) attempts to generate a PDF, an unhandled exception is thrown if the Default PDF Format value is not yet stored in the WorkPointSettings list:
Workaround
Open Template Management Settings in WorkPoint 365 administration, choose a value for Default PDF Format, and save. This stores the setting, avoiding the unauthorized write attempt during PDF generation.
Status
Known bug. We will resolve this issue in version 4.26.
Description
When performing a manual synchronizing of SharePoint groups from the root site to a bucket site collection, groups that contain the root site’s title in their name are created but do not receive the expected permissions.
The issue is limited to bucket site collections.
In the log you will observe the following warning:
Workaround
Rename the relevant SharePoint Groups on the root site to not include the root site title or rename the root site title prior to synchronizing SharePoint groups from the root site to a bucket site collection.
Status
Known bug. We will resolve this issue in version 4.25.
Description
When configuring a process in WorkPoint Automate with the "Copy or move documents" step comfigured to run in "Move Mode" the modified date of the moved document is not preserved.
Workaround
Currently there is no workaround.
Status
Known bug.
Description
After exporting a solution from a tenant and importing it into a separate tenant, the following issues are observed:
- Web Parts only function on the root site but fail on module master sites
- The Express Panel does not work.
- Multiple HTTP requests fail when loading the page.
- It appears that the system is attempting to retrieve WorkPoint Settings from the original exported solution that naturally fails with an 403 Forbidden error.
Root Cause
Incorrect SolutionUrl reference in the exported package.
Workaround
Correct the SolutionUrl property in SiteCustomActions on affected Master Site Collections using PnP PowerShell.
By modifying the SolutionUrl to reflect the URL of the tenant the solution was imported to, the issue should be resolved.
Status
Known bug. We will resolve this issue in version 4.24.
Description
When configuring a process in WorkPoint Automate to create an entity site with the synchronous setting, the process fails with the following exception if no buffer sites are available:
"An action cannot be executed because a connection is not configured or expired. Please go to process builder and create a new connection."
Even though the process is set to synchronous execution, it still requires a connection when no buffer sites are available. This behavior is not clearly communicated in the UI or documentation.
Workaround
Configure a Connection for WorkPoint Automate Steps.
Status
Known bug. We will enhance the guidance in the UI in version 4.25.
Description
When accessing job execution logs via the "Open" link in WorkPoint 365 Administration, the loggingStartTime and loggingEndTime in the generated URL may contain incorrect values.
- The start time may be set far in the future (e.g., year 3625).
- The end time may default to January 1, 1601, which is likely an uninitialized or default value.
This results in an invalid time range, making it difficult to review execution details and identify errors.
Workaround
Instead of using the generated URL, follow these steps to access the correct log data:
-
Copy the "Current WorkPoint Scope ID" from the generated logging URL.
- Example: The loggingScopeId parameter in the URL contains this ID.
- Go to the WorkPoint Event Logging administration page.
- Paste the copied Scope ID into the "Filter Query" field.
- Run the search to retrieve the relevant logs.
This method ensures that you can access the correct log data without relying on the incorrect timestamps.
Status
Known bug. We are currently evaluating which release will include a fix.
Description
Open the Microsoft List Web App and click on a business module list:
Run a process:
Observe that loading the process hangs and never finishes:
Workaround
Access the business module list directly from within WorkPoint 365
Status
Known bug. This issue will be resolved in version 4.26.
Description
When configuring a search setting with the "Tenant-wide search" option enabled, the search results span the entire tenant:
The search results in the Express Panel now correctly reflect the settings with the "Tenant-wide search" option enabled:
However, the Search Form Step in a WorkPoint Automate process does not return the expected results:
Workaround
None identified yet.
Status
Known bug. This issue will be resolved in version 4.25.
Description
When selecting "Delete" on a single failed job in the WorkPoint Job Queue:
It results in the following error message:
Workaround
Select multiple failed web jobs and delete them simultaneously.:
Status
Known bug. This issue will be resolved in version 4.25.
If a user includes a period (".") in the document title, the UI interprets it as the start of a file extension, affecting how the file type is displayed.
Workaround
None identified yet.
Status
Known bug. This issue will be resolved in version 4.24.
Description
When running a Master Site Sync, you may encounter the following exception in the WorkPoint Administration Event Log:
WorkPoint.Core.SiteReplicator.AddWebPartsToTargetPage
This error occurs when attempting to sync wiki site pages.
Workaround
Delete the wiki pages from the master site before running the Master Site Sync.
Status
Known bug. This issue will be resolved in version 4.24.
Description
When using a Search Form Process Step to search for entities and display a view containing a specific date, the date format does not match the format used in SharePoint.
The date format displayed in SharePoint entity list:
The date presented in the Search Form Process Step:
Workaround
None identified yet.
Status
Known bug. This issue will be resolved in version 4.25.
Description
Localized stage names are not applied. For example, in a Danish browser, the stage "Potential" is displayed in English instead of the localized Danish name "Potentiel."
Stage Translations:
Process Entity Form:
The standard change stage process displays translations as expected. This issue occurs specifically during entity creation in the Process Builder, where the configured localization's are ignored.
Status
The issue is planned to be resolved in version 4.25
Description
An unexpected error occurs when attempting to create a notification. The error message displayed is: "Nullable object must have a value." This issue arises during a simple process that is expected to send a notification.
Root Cause
In the notification settings, the following values are null:
- NotificationPriorityTermSetId
- NotificationTypeTermSetId
These values are required for proper operation.
Workaround
Open the Site level term groups on the root site in classic mode to get the term set ID for "WorkPoint365 Notification Priority" and "WorkPoint365 Notification Type":
Before performing the steps below ensure a backup is made of the workpointsettings list and ensure version history is enabled on the workpointsettings list.
- Open /sites/lists/workpointsettings
- Locate the key WP_NOTIFICATION_SETTINGS
- Copy the content of the value field to a suitable editor
- Locate and insert the term set ID's for NotificationPriorityTermSetId and NotificationTypeTermSetId that currently are null:
Now save the changes made to the WP_NOTIFICATION_SETTINGS value field.
Before the changes are implemented, you need to open WorkPoint Cache Management and clear the cache by selecting "Solution and Taxonomy" and then clicking the Clear button:
Status
Known bug. The issue will be resolved in version 4.25
Description
When importing a solution, the process fails, and the following error appears in the WorkPoint administration event log:
- Message: Object reference not set to an instance of an object.
- Exception type: System.NullReferenceException
- Failed method: WorkPoint.Core.Helpers.InheritanceHelper+<>c__DisplayClass2_0.<AddMissingInheritanceFields>b__0
Root Cause
The issue arises when a list used in the inheritance settings is stored with a different URL than the one created on the master site during the import. This can occur under the following conditions:
- A list or field used in inheritance settings has been renamed.
- The inheritance settings were not updated after the renaming.
- An export and subsequent import of the solution were performed without updating the inheritance settings to reflect the new list name or field name changes.
Workaround
- Before exporting the solution, review all inheritance settings.
- Verify that the list and field titles in the inheritance settings correspond to the correct list and field names and URLs on the master site.
- Update the inheritance settings to reflect any recent changes to list names or URLs.
- Proceed with the export and import after confirming the settings are correct.
Status
Known bug. Better handling of the exception will be addressed in version 4.24.
Description
When creating a Case (or equivalent entity, depending on the solution configuration), selecting a parent entity directly from the entity form (1) in the process will fail upon saving. However, selecting a parent entity from the panel on the right (2) works without issue:
Workaround
Advise end users to use the panel on the right to select a parent entity as a workaround.
Status
The issue has been logged, and a solution is under consideration and will be implemented in version 4.24
Description
In WorkPoint Express, it is not possible to drag and drop selected documents to rearrange their order when using a WorkPoint Automate Process with a Multiple Items Properties Form that has the Enable Sorting option enabled:
Root Cause
This issue is specific to WorkPoint Express and affects the functionality of the Enable Sorting option in the Multiple Items Properties Form.
Workaround
Execute the process from a web browser instead of WorkPoint Express. The sorting functionality works correctly in the browser.
Status
Known bug. This issue is scheduled to be resolved in version 4.24
Description
The finish section of a Process Builder Step has the following Redirect setting:
When executing the process and reaching the final step with a configured redirect, clicking the designated redirect link behaves as follows:
The built-in browser Popup and Redirect Blocker settings may prevent a new tab from opening. This is indicated by an icon in the browser's address bar:
Workaround
The users can change the behavior in the browsers settings or the IT-department can configure a central browser policy to allow popup and redirects on the site
Status
Known bug: A notification will be implemented to inform users when a new tab cannot be opened due to the browser's popup and redirect restrictions. This fix will be included in version 4.24
Description
We currently don't support synchronizing Search Settings during default site provisioning and it's not available as a selectable synchronization scope.
Expected Behavior
It should be possible to sync Search Settings from the Master Site
Status
Known limitation, we will support this in version 4.25
Description
An issue has been identified where the 'When an item is published' trigger in Process Builder fails to execute the intended processes when content changes occur in a file, rather than metadata changes alone.
Expected Behavior
The process should trigger when a minor version is published after content changes.
Current Behavior
The process does not trigger under the conditions described above.
Root Cause
The event fails to register file content changes correctly when versioning settings are enabled.
Additional Notes
See SharePoint Online versioning settings for configuration details:
The expected event trigger behavior should be as demonstrated here:
Workaround
None identified yet.
Status
Known bug. Will be resolved in version 4.24.
Description
When running a WorkPoint Automate process that includes document conversion to PDF, an error may occur when processing a large number of documents or handling large file sizes.
The following error message will be displayed:
Workaround
The "Converts selected documents to PDFs" should be set to run async:
Status
Known bug. Better error message if there is time out on the API due to the file size. User should be informed that they must run the process async.This issue will be resolved in version 4.24.
Description
Users are unable to remove or deselect values in a multi-select Managed Metadata field within the WorkPoint wizard. When multiple terms are selected, they cannot be removed from the input field.
Example
A user selects "PNC" and "OFI" in the wizard but cannot remove these terms once selected.
Workaround
Start at the end of the entered terms and use backspace to delete selections.
Scope
- Issue only occurs within WorkPoint Wizards.
- The issue does not affect WorkPoint Automate processes.
Status
This issue will not be fixed in WorkPoint Wizards, as it works as intended in a WorkPoint Automate Process.
Description
The Related Content feature on the WorkPoint platform fails to display any results.
Observed Result
No related content is displayed. Network inspection (developer tools in the browser) shows a failed GetRelatedContents request.
Expected Result
Related content should be displayed based on the selected email or document.
Workaround
None identified yet.
Status
Known bug. This issue will be resolved in version 4.23.
Affected Versions
This issue affects solutions installed after version 4.20.
Description
When installing a new solution after the release of version 4.20, the Template Library Actions command set is not added to the Template Library. As a result:
- Navigate to the Template Library.
- The buttons "New Word Template" and "New Excel Template" are missing from the ribbon
Root Cause
The issue is caused by the NoScriptSite setting.
Workaround
- Ensure that the site does not block custom scripts (NoScriptSite = False) before adding a new WorkPoint 365 solution.
- There is currently no way to add the missing buttons to existing solutions after installation.
Status
Known bug. We will release an update that automatically adds the missing command set to the Template Library if it is not present. Release date still to be determined.
Description
When deleting an entity from the business module list, the associated site is not marked for deletion if the site collection is a NoScript site. The entity itself is removed from the business module list, but the site remains active.
Workaround
Currently, there is no direct workaround, but manually updating the NoScript setting before deletion may help mitigate the issue.
Status
Known bug. This issue will be resolved in version 4.24.
Description
In a system process triggered by stage changes, only the first step in the process has access to the _before values from the entity whose stage was changed. Subsequent steps are unable to retrieve or use these values, leading to unexpected behavior in workflows that rely on historical data.
Root Cause
The _before values are only available in the first step after the stage change is triggered. They are not persisted throughout the entire process execution, causing subsequent steps to operate without access to the original data state.
Workaround
None identified yet.
Status
Known bug. This issue will be resolved in version 4.23.
Description
When for example using a lookup field to associate a contact with a company from the Contacts list, the following issues are observed:
- Not all contacts from the Contacts list are displayed in the lookup field when accessed by clicking in the field:
In the search panel to the right, the same behavior occurs.
- The type-ahead functionality in the lookup field also does not function as intended, leading to difficulties in finding specific contacts:
No result when only typing part of the first name:
Result when typing the complete first name:
Expected Behavior
- The lookup field should display all contacts from the connected Contacts list.
- Typeahead should allow users to search and find specific contacts efficiently.
Workaround
Use the search option on the right panel to search and select a specific contact.
Status
This issue is scheduled to be resolved in version 4.23
Description
An issue occurs during buffer site and site creation when the Master Site contains a "Full Width" section. This prevents successful synchronization.
Error Details
In the WorkPoint 365 administration Event log, the following exception is observed during the Master Site Sync process: PnP.Core.ClientException at PnP.Core.Model.SharePoint.PageWebPart.ToHtml
Workaround
Use a normal section with a text web part instead of a "Full Width" section.
Status
Known bug, will be resolved in version 4.21 (ID43980)
Description
An UI issue occurs in a WorkPoint Automate user process with the 'Multiple lines of text' column type with the enhanced rich text option in SharePoint Online (SPO). When different options are used in the editor, the dialogs remain open and do not close as expected.
Expected Behavior
Dialogs should close after selecting options in the enhanced rich text editor.
Status
Known bug, under investigation. (ID44623)
Description
When a user creates a document from a template through a Wizard, they receive the error message: "Document Provisioning failed".
However, the document is still created successfully.
Error Log Entry: WorkPoint administration event log:
Exception / OuterMessage
The collection has not been initialized. It has not been requested, or the request has not been executed. It may need to be explicitly requested.
Additional Behavior
The issue also occurs when using a WorkPoint Automate process. The error message displayed: "The document with the same name does not already exist.":
Impact
Affects some solutions.
Status
Known bug. This issue will be resolved in version 4.21. (ID45237)
Description
An issue has been identified where the command bar (toolbar) is missing from the default SharePoint Online Documents webpart in WorkPoint 365 on SharePoint pages. The issue does not affect all instances but appears to occur randomly across different solutions.
Expected Behavior
The command bar should be visible and functional within the Documents webpart in WorkPoint 365 when enabled.
Status
Known bug.
Root Cause
The issue seems related to a SharePoint framework change as described here: GitHub Issue #10077.
Additional Notes
Microsoft has acknowledged the issue and is working on a fix roll-out as per the GitHub discussion.
Comments
14 comments
Known bugs and limitations updated.
Known bugs and limitations updated.
Known bugs and limitations updated.
Added: Web Parts Not Working on Modules After Import to a New Tenant (ID46661) and Copy or move documents Step in Move Mode does not preserve Modified date (ID46725)
Known bugs and limitations updated.
Added: SharePoint Group Sync Fails on Bucket Site Collection if Root Site Title is in Group Name (ID46775)
Known bugs and limitations updated.
Added: UnauthorizedAccessException when generating PDF without Default PDF Format saved (ID46858)
Known bugs and limitations updated.
Added: WorkPoint Express does not load in the right task pane in Microsoft Word version 2502 (Current Channel) (ID45193)
Known bugs and limitations updated.
Updated: WorkPoint Automate Process not triggering on 'When an Item is Published' (ID43574)
Known bugs and limitations updated.
Resolved in version 4.23
Known bugs and limitations updated.
Changes to Search Settings on a Master Site are not synchronized during site creation (ID44879) moved to 4.25
Hi, question on ID45193.
When is WPE 6.11.1 planned for release?
Hi Bjørn
Testing have just been completed, so in the near future the release will be ready.
Hi Per.
Do you have any ETA on WPE 6.11.1?
Hi Jakob
After Easter.
Known bugs and limitations updated.
WorkPoint Express does not load in the right task pane in Microsoft Word version 2502 (Current Channel) (ID45193)
Please sign in to leave a comment.