Changing UiPath Package Location to SharePoint/Shared Folder: Impact and Considerations

News Knowledge Base
1

Changing UiPath Package Location to SharePoint/Shared Folder: Impact and Considerations

When considering moving the NuGet package location in UiPath Settings to SharePoint or a shared folder, it's crucial to understand the potential impact and considerations:

  1. Local Machine Requirement:
  • Moving the package location to SharePoint is not recommended, as it must reside on the local machine. This is essential for optimal performance, as programs need to be locally accessible for efficient execution, involving copying to RAM.
  1. Execution Issues with Network Disconnections:
  • Utilizing a network-based location can lead to execution issues. Any network disconnection or intermittent drops may disrupt the execution process, causing delays or failures.
  • Local Machine Advantage:
    • Local package storage ensures faster access, enabling UiPath processes to efficiently load into RAM during execution.
  • Network-Based Considerations:
    • Network-based locations introduce dependencies on network stability, making the execution susceptible to disruptions.