Can we store Office Script (.osts files) in a on-premise SharePoint folder?

Grace 0 Reputation points
2023-10-23T10:35:09.36+00:00

We have neither OneDrive nor SharePoint Online within the business.

However, we have On-Premise SharePoint server on site.

Can we store Office Script (.osts files) in a on-premise SharePoint folder?

I hoped to run script using power automate flow, and currently stuck in scripts' generating and storage.

Office Development
Office Development
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Development: The process of researching, productizing, and refining new or existing technologies.
3,497 questions
Office Management
Office Management
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Management: The act or process of organizing, handling, directing or controlling something.
2,007 questions
SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,806 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Barry Evanz 235 Reputation points
    2023-10-27T12:08:57.6833333+00:00

    You can indeed store Office Script (.osts files) in an on-premise SharePoint folder. However, there are a few essential considerations to bear in mind to ensure a seamless experience. It's important to note that scripts with external calls cannot be executed directly from SharePoint due to current limitations – you may encounter an error regarding network access calls. Power Automate does offer support for running scripts stored on SharePoint, specifically through the "Run script from SharePoint library (Preview)" action.

    To securely store your Office Script (.osts files) in an on-premise SharePoint folder, follow these straightforward steps. Begin by opening the Office Script you intend to store in SharePoint. Select the "More options (…)" menu and opt for "Save as." In the ensuing file picker, designate the specific folder within your SharePoint site where you wish to store the script. Simply click "Save." Upon saving the script in SharePoint, you gain the capability to execute it using the "Run script from SharePoint library (Preview)" action within Power Automate.

    As an interim measure, we suggest a practical workaround. Convert the Word document to PDF using a dedicated PDF conversion tool, such as Adobe Acrobat Reader or Microsoft Word. Following this conversion, print the PDF document directly, bypassing Word Online's PDF conversion process. This approach should ensure that the resultant PDF maintains the integrity of the original Word document. It provides a dependable solution while allowing for further investigation into the root cause of the Word Online issue. Should you require technical assistance, please let us know, and we'll be happy to provide guidance or code samples where applicable.

    For optimal efficiency and organization, here are some additional tips for handling Office Script (.osts files) in SharePoint. It's advisable to establish a dedicated SharePoint library for storing your Office Scripts, streamlining management. Leverage SharePoint permissions to control access to these scripts. When creating a Power Automate workflow for running a script from SharePoint, ensure accurate selection of the SharePoint library and file path. Furthermore, consider using Power Automate to automate the process of saving and executing Office Scripts, offering potential for increased productivity.

    0 comments
  2. Hariharasuthan Mani 0 Reputation points
    2024-04-16T12:35:30.55+00:00

    We have activated the office scripts in our business microsoft 365. However we did not receive automate option excel. Could you please let me know how we fixed this issue.

    0 comments