Skip to content

List templates created from a list do not include Automate rules, and there is no way from CSOM to retrieve or create one #9875

Closed

Description

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint CSOM

Developer environment

Windows

What browser(s) / client(s) have you tested

  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Additional environment details

  • CSOM v 16.1.25110.12000

Describe the bug / error

When creating a site template the information regarding Automate rules is not saved in the template, and recreating a list from a template will not copy it over. PnP uses the site script to retrieve and create any rule on a list, but has no way to save the content in a site script. There should be a way to save the rules with a switch (as done for the data) in the List.SaveAsTemplate() call or alternately a way to access, retrieve, create and execute site scripts to allow users to access "modern" features also via CSOM (as the underlying API is a REST API.

Steps to reproduce

  1. Save a template via List.SaveAsTemplate()
  2. Create a list specifying the previously created template in the ListCreationInformation object
  3. Open the old and new list in top bar -> Automate -> Rules -> Manage Rules, they do not match.

Expected behavior

The rules (as well as any modern features) can be selected to be saved in the template and subsequently recreated on template usage. Alternately, expose the site script retrieval and execute REST APIs in CSOM as they are already exposed and useable in PnP to circumvent the issue.

Activity

  1. Ashlesha-MSFT commented on Jun 3, 2025

    @Ashlesha-MSFT
    Contributor

    Hello Marco Antonio Mauro (@marcus905),
    Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

  2. Ashlesha-MSFT commented on Jun 3, 2025

    @Ashlesha-MSFT
    Contributor

    Marco Antonio Mauro (@marcus905),
    This behavior is currently by design, as the List.SaveAsTemplate() method does not support saving Power Automate rules or other modern list features. Since this functionality isn't implemented yet, it would fall under a feature request rather than a bug.

    To help improve the product, we recommend raising this request on the official SharePoint Feedback Portal so it can be reviewed by the engineering team: aka.ms/sp-dev-uservoice

  3. self-assigned this
    on Jun 3, 2025
  4. added
    type:uservoice-requestEnhancements & feature requests should be posted: http://aka.ms/sp-dev-uservoice
    on Jun 3, 2025
  5. marcus905 commented on Jun 3, 2025

    @marcus905
    Author

    @marcus905, This behavior is currently by design, as the List.SaveAsTemplate() method does not support saving Power Automate rules or other modern list features. Since this functionality isn't implemented yet, it would fall under a feature request rather than a bug.

    To help improve the product, we recommend raising this request on the official SharePoint Feedback Portal so it can be reviewed by the engineering team: aka.ms/sp-dev-uservoice

    Hi, but there is also no way to manually edit those via a CSOM API. That's probably a bug, as API should have feature parity with UI.

  6. VesaJuvonen commented on Nov 3, 2026

    @VesaJuvonen
    Contributor

    This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.

  7. github-actions commented on Nov 3, 2026

    @github-actions

    Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

    If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

    We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Needs: Triage 🔍Awaiting categorization and initial review.sharepoint-developer-supportsharepoint-developer-supporttype:archive-old-issueIssues which are closed as tool old for active worktype:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.type:uservoice-requestEnhancements & feature requests should be posted: http://aka.ms/sp-dev-uservoice

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions