Skip to main content

Known bugs and limitations

  • Updated
  • Reading time: —

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.

Technical Limitation – Microsoft 365 Baseline Security Mode

Overview
It has been identified that certain Microsoft 365 tenants have activated Baseline Security Mode. While this feature enhances the security posture of a tenant, it currently introduces a limitation regarding Custom Scripts across all sites.

When this mode is active, Microsoft 365 enforces a restriction that prevents the temporary enablement of custom scripts, which is currently required for specific WorkPoint 365 operations.

Impact on WorkPoint 365
WorkPoint 365 utilizes custom script capabilities to perform essential configuration tasks. If Baseline Security Mode is enabled, the following processes are currently affected:

  • Entity Management: Setting the NoCrawl property on a Web when an entity is deleted or restored.
  • Provisioning & Sync: * Connecting entities and sites through the Web Property Bag during site creation or Master Site sync.
    • Setting Site Collection properties during initial creation.
    • Syncing property bag entries at the Site Collection level.
  • App Lifecycle: Installing or updating the Modern UI app within the Tenant App Catalog.
  • Buffer Site Management: Updating the ServerRelativeUrl when buffer sites are taken into use.

Future Support & Roadmap
WorkPoint is committed to supporting Microsoft's security standards. We are currently developing updates to our core engine to ensure full compatibility with Baseline Security Mode.

Future releases will transition these processes to methods that do not rely on custom scripts, allowing you to maintain a high-security baseline without impacting WorkPoint functionality.

Recommendation
If you experience issues with site provisioning or property syncing, please verify if Baseline Security Mode is active in your tenant:

  1. Navigate to Settings > Org Settings in the Microsoft 365 Admin Center.
  2. Go to the Security & Privacy tab.
  3. Check the status of Baseline Security Mode.
  4. If enabled, we recommend making adjustments, to ensure custom script capabilities aren't blocked.
Default WorkPoint 365 Automate Create Entity Process lookups only find SharePoint list items when the search matches the start of the Title

Description:
Currently, this is expected behavior in the standard WorkPoint 365 Automate Process Create Entity Step. When a lookup field is configured to source values from a SharePoint list, the lookup search only returns items where the entered text matches the beginning of the Title value. Items that contain the text later in the Title (for example searching a last name when Title starts with a first name/initials) will not be returned, even though they exist in the list. This behavior can also be seen in custom processes using the same type of lookup.

Cause:
The standard SharePoint list lookup search uses a “starts with” match on the Title field, rather than a “contains” match.

Workaround:
If the lookup targets a WorkPoint 365 Business Module list, create a view that includes only the Title column and set it as Default view used in lookups in the Business Module’s General Settings. This enables a broader “contains” style search for that Business Module lookup.

Status:
We are aware of this behavior. Use the workaround above where applicable.

Buffer Site & Site Creation Fails Due to Classic Publishing Feature Restriction

Description:
When creating a buffer site or a new site collection, the operation fails with an exception stating that activation of the SharePoint Server Publishing Infrastructure feature is not allowed.

The complete message:
“Error when activating Site Collection feature SharePoint Server Publishing Infrastructure Activation of classic publishing feature is not allowed.”

This behavior occurs if the feature is active on the master site collection.

Cause:
Starting September 15, 2025, Microsoft has disabled creation of new classic publishing sites and blocked activation of publishing features in SharePoint Online. This change is part of Microsoft’s modernization strategy and applies to both user interface and API-based site creation.

Existing classic publishing sites continue to work as usual, but new classic publishing sites cannot be created, and publishing features can no longer be activated on new site collections.

Workaround:
If classic publishing features are not in use, disable them on the master site collection. After disabling the feature you also need to ensure that the list ReusableContent is hidden on the master site.
If publishing features are required temporarily, tenant administrators can enable the following setting via PowerShell until March 15, 2026:Set-SPOTenant -AllowClassicPublishingSiteCreation $true

Status:
This is expected behavior due to Microsoft’s enforcement of modern SharePoint site standards. WorkPoint recommends disabling the Classic Publishing Feature on the Master Site Collection if not in use.

Copy or move documents Step in Move Mode does not preserve Modified date (ID46725)

Description
When configuring a process in WorkPoint Automate with the "Copy or move documents" step configured to run in "Move Mode" the modified date of the moved document is not preserved.

Workaround
Currently there is no workaround.

Status
Known bug.

Process Fails on "Converting to PDF" with Large Files – Requires Async Execution (ID42301)

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.

PDF Combine Fails When Page Sizes Differ (ID48472)

Related articles

Comments

42 comments

Date Votes
  • Per Schulze

    Known bugs and limitations updated.

    Added:
    Process Builder – Lookup from Calculated Column with Multiple Values Does Not Display Full Value (ID48572)

    0
  • Per Schulze

    Known bugs and limitations updated.

    Added:
    Edit Tab View settings fails after importing solution with a module excluded (ID58546)

    0
  • Per Schulze

    Known bugs and limitations updated.

    Added:
    External Sharing – Invited Guest Users Do Not Receive Correct Access Until Cache Refresh on Root SiteUserInfoList (ID58205)

    0
  • Per Schulze

    Known bugs and limitations updated.

    Added:
    Regular Users Cannot Edit Relations in WorkPoint Automate Process (ID59042)
    Data Import fails if Stage Mapping Field Is included In Import (59048)

    0
  • Per Schulze

    Known bugs and limitations updated.

    Added:
    Buffer Site & Site Creation Fails Due to Classic Publishing Feature Restriction

    0
  • Per Schulze

    Known bugs and limitations updated.

    Moved to resolved in version 4.27 (Released tonight between 19:00-22:00 CET)

    • Regular Users Cannot Create Or Edit Relations in WorkPoint Automate Process (ID59042)
    • WorkPoint Process Step Loses Configuration When Switching Between Two 'Send HTTP Request' Steps (ID48523)
    • Parent Entity Title Not Displayed in Lookup Field During Process Execution (ID47709)
    • Teaching bubble and navigation doesn't work on sub process (ID47317)
    • Access denied when removing deletion mark from site in Entity Site Recycle bin on NoScript sites (ID47292)
    • Localized stage names are not applied in Process Builder Entity Form (ID46023)
    • "Enable Sorting" Option Not Working in Multiple Items Properties Form in WorkPoint Express (ID45822)
    • Issue with Redirects and Auto-Execution of Site Links in "Open in a New Tab" Due to Built-in Browser Popup and Redirect Blocker (ID45295).
    0
  • Per Schulze

    Known bugs and limitations updated.

    Added:
    Folder Copy Does Not Trigger New Document IDs (ID50081)
    Document opening in WorkPoint Express 365 ignores SharePoint “Open in App or Browser” setting (ID49932)

    0
  • Per Schulze

    Known bugs and limitations updated.
    Moved Outlook Actionable Adaptive Card Emails Render Blank in Specific Mail Flow Configurations (ID48555) to resolved.
    Archived WorkPoint Express does not load in the right task pane in Microsoft Word version 2502 (Current Channel) (ID45193) (added 32bit Office download option)

     

    0
  • Per Schulze

    Know bugs updated

    Added:
    Deleting an HTTP Endpoint Credential Can Break Remaining Endpoints (ID50979)
    MasterSite Sync “Total items” count is inflated when entities lack a Site (ID50974)
    Truncated Title in Search Entity Form Results (ID50826)
    Outlook Classic Does Not Journal Emails Opened in a Separate Window (ID50884)

    0
  • Per Schulze

    Known bugs and limitations updated.

    Moved to resolved in version 4.28:
    Folder Copy Does Not Trigger New Document IDs (ID50081)
    External Sharing – Invited Guest Users Do Not Receive Correct Access Until Cache Refresh on Root SiteUserInfoList (ID58205)
    Process Builder – Lookup from Calculated Column with Multiple Values Does Not Display Full Value (ID48572)
    Teams Tab Links on Master Site Point to Master Resources Instead of Entity-Specific Ones (ID48504)
    Copy entity removes Quick Navigation elements linking to site pages (ID48374)

    0
  • Per Schulze

    Known bugs and limitations updated.

    Added:
    Technical Limitation – Microsoft 365 Baseline Security Mode
    Default WorkPoint 365 Automate Create Entity Process lookups only find SharePoint list items when the search matches the start of the Title

    0
  • Per Schulze
    • Edited

    Know bugs and limitations updated.

    Added:
    ItemLocation not updated for child entities after parent relocation (ID51588)

    0

Please sign in to leave a comment.