Altium 365

Our Knowledge Base is developed from our users questions. Find answers and step-by-step instructions. Chances are we’ve seen your question before.

A365

KB: "Failed to get default model link from template" when creating a component

When creating a component in Altium 365, the error "Failed to get default model link from template" may appear for certain components. This occurs when the template’s predefined symbols or footprints cannot be found. The original schematic or footprint might have been deleted, replaced, or moved. To resolve this, you need to verify and update the linked models in the component template.

A365

KB: 404 Error when accessing the Requirements and Systems Portal

Users may encounter a 404 error when accessing the Requirements and Systems Portal (RSP) in Altium 365, due to the RSP space not being created for their workspace. To resolve this, users must contact their Altium account manager and provide workspace details to initiate RSP space creation. Once setup is complete, the portal becomes accessible via the nine-dot menu in Altium 365.

A365

5

1

KB: Altium 365 Data Cleanup

How to remove all objects related to components, projects, templates, etc.

A365

3

KB: Altium 365 workspace size

Data is stored in different ways depending on the type of information. This article also covers how to find the size of certain items in your workspace.

A365

0

1

KB: Apply lifecycle states to project

The “Project” represents a managed project whose data is stored in the repository under version control (Git/SVN) on its own. Currently, the lifecycle state is not implemented for these repository contents and is sit on the initial “Planned” state always.

A365

KB: Azure SSO User Provisioning Fails with 400 Error Due to Existing Account Conflict in AltiumLive

User provisioning via Azure SSO to AltiumLive may fail with a 400 Bad Request error if the user already exists in the AltiumLive database under a different organization or as a self-registered account. This conflict prevents the Identity Provider (IDP) from creating the user in the intended company account. The issue typically arises when the same email address is already associated with another organization in AltiumLive. This article explains the root cause and provides resolution steps, including reviewing provisioning logs, configuring email domains, and contacting support for account transfers.

A365

KB: Cannot Release Requirements in Altium 365

Users attempting to release a set of requirements in RSP may encounter a missing "Release" option in the interface, even when the requirement state is set to "Final". This issue is typically caused by a configuration setting that disables version management features. To enable the release functionality, users must activate the Version Management flag in the system settings. Once enabled, the release process follows the standard steps outlined in Altium’s documentation.

A365

KB: Cannot save project due to Git Error with status code 471

The git server of an Altium 365 workspace has protection against misuse: it does not allow binary files larger than 256 MB of the following types: zip, 7z, and rar. Pushing those files to repositories can lead to significant slowdown in both client-side and server-side processing of customer data, up to denial of service. Once the user tries to save such a file to the server from Altium designer, the save operation will be rejected by the server with the Git Error: request failed with status code 471

A365

1

KB: Change folder path location of managed project

If you want to pull the master server project repository to a local folder path different from the previous/default or change the local folder path before pushing it back to the master server project repository. The folder path can be changed in Preferences as a default behavior, or on the fly in File » New » Project, or File » Open Project dialog. If the project folder is moved locally again, the dialog prompts you to confirm the new folder path upon opening the project. The default folder path location C:\Users\Public\Documents\Altium can be modified in Preferences, Data Management » Design Repositories, Properties. Or, on the fly, you can specify each time during project creation or pull a project from the server to a custom local path. If the project folder is moved locally again, File » Open Project, Browse.., navigate to the new location and double-click on *.PrjPCB, upon which you are prompted to use the path as a new location for your local repository for the project.

A365

0

3

KB: Change project release revision naming scheme

I have a project in Altium 365 cloud which already have one release done, and I want to change project release number from standard scheme A.1 to something else.

A365

KB: Change the lifecycle state for all components in a project at once

Once components are used in a project, it is sensible to change their lifecycle states, for example from Draft to Prototype. All components that have been used in a project can have its states changed in one go in Explorer panel.

A365

KB: Control permissions on lifecycle transition of managed objects in Altium 365

Permissions for lifecycle transitions of managed objects in Altium 365 can be controlled based on subscription levels. With Pro and Enterprise subscriptions, lifecycle definitions and permissions can be configured to allow specific users or groups to manage transitions. The Enterprise level offers additional workflow control, including approval-based transitions for more structured oversight. This setup ensures better management of version control and access rights, particularly in collaborative environments.

A365

KB: Create and add templates referenced by projects managed in Altium 365 workspace

Templates can be created and added for projects managed in the Altium 365 workspace, either as new files or by migrating existing local templates.

A365

KB: Decipher Altium 365 workspace items with prefix ID of BLI

Your Altium 365 workspace might contain some so-called BLI ( Bom Line Items), which are created when a design is uploaded that uses components which are not managed in the same workspace.

A365

4

5

KB: Delete an Altium 365 Workspace or change its ownership

If an Altium 365 workspace is no longer in use and/or it is preventing the current owner from joining another organization/account, the workspace can be deactivated either by the owner or the Group Administrator of the organization on the workspace tab of their profile page (or company dashboard) or its ownership can be changed to another active user by a Group Administrator from the company dashboard.

A365

KB: Delete items from Altium 365 Workspace permanently

Delete an item from Altium 365 Workspace permanently. The delete Item command in the Explorer panel is a soft delete that moves the item to Trash. From here, the item can be deleted permanently, granted there are no parent items referring to it. Access your workspace at 365.altium.com, click on Trash to open its pane, select the item, and hit the 'Permanently Delete' button

A365

KB: Duplicate item HRID error for new release item

When attempting to create a new release item with the same name as a previously abandoned item in Altium 365, users may encounter the error “Duplicate item HRID error for new release item.” This occurs because release items are server-controlled, and their Item ID remains reserved even if the item is set to an abandoned lifecycle state. To resolve this, users can either rename the new item, delete the old one, or abandon only the revision instead of the entire item.

A365

KB: Edit Name or Description of items managed in Altium 365 workspace

Edit the Name or Description of items managed in the Altium 365 workspace. A popup dialog is presented when right-clicking 'Properties...' on an item managed in the Altium 365 workspace in the Explorer panel, such as component and template. The title and Description fields here are read-only as the item has already been released in the version control. To modify them, you will need to go through another release. Right-click and 'Edit..., make necessary changes, and Save to Server (Ctrl+Alt+S)

A365

KB: Fail to Download Files for Revision - 403 Forbidden

Users may encounter the error message “Failed to download files for revision. 403 forbidden” when updating Draftsman templates or previewing models in the Explorer. This issue is typically caused by network restrictions such as firewalls or proxy settings that block required URLs or ports used by Altium Designer. To resolve the issue, users should consult with their IT team to ensure that all necessary URLs and ports are whitelisted according to Altium’s connectivity requirements.

A365

KB: Git Error "Failed to write chunk header" when saving to workspace

Users may encounter the error “Git error: failed to write chunk header: The connection with the server terminated abnormally” when committing a project to the workspace, resulting in failure to save changes. This issue is typically caused by either a hidden Git repository in a parent directory or a misconfigured WinHTTP proxy. To resolve it, users should inspect their folder structure for conflicting Git repositories and reset any outdated proxy settings. A fresh checkout of the project into a clean directory can also serve as a workaround.

A365

KB: Graphics Support in Altium 365 Web Viewer Interface

This knowledge article details the limited support of graphics in Altium 365's web-browser interface.

A365

KB: How many Organizational Security Package (OSP) seats do I need?

An Altium 365 workspace has different data access levels: Workspace Member, Guest User, and Share with Organization User. The article explains how to find the number of OSP seats needed.

A365

KB: How to delete or remove the duplicate dynamic parameters created by the PLM Component sync

Some duplicate dynamic component parameters were added to the Altium components during the PLM Component Sync. Deleting this dynamic parameter in a single component editor is impossible. How do you delete this parameter?

A365

KB: How to edit components in Altium 365

Working with and editing managed components in Altium 365

A365

KB: How-To Altium 365 Workspace Members Bulk Addition and Deletion of Users

If there is a requirement to add multiple users to an Altium 365 workspace Workspace Members list, this can be done using a suitably formatted list of email addresses. If there is a requirement to remove multiple users from an Altium 365 workspace Workspace Members list, this is not possible, users must be removed manually and one at a time. There may be a small subset of contexts where bulk removal of users can be done by deactivating (deleting) a workspace, and then creating (activating) a new one.

A365

KB: Import file-based library components to Altium 365 workspace

Import file-based library components to Altium 365 Workspace. Use Library Importer to migrate file-based library components to Altium 365 Workspace. Invoke File » Library Importer.

A365

1

KB: Lost Connection to Altium 365 While Working

Connections to the Altium 365 platform may occasionally be lost due to various reasons, such as service provider outages, server issues, or temporary disconnects. This article explains how such situations are handled from the server's perspective.

A365

1

1

KB: Owning More Than One Workspace

Organizations are generally limited to a single Workspace. This article outlines the options for supporting multiple Workspaces within an organization.

A365

KB: Re-add a project under Altium 365 version control cleanly

How to re-add a project under Altium 365 version control cleanly, such as those once deleted from Altium 365, brought from external VCS, added to Altium 365 without version control enabled, etc.

A365

2

KB: Recall or roll back a revision of project already released to manufacture in Altium 365

Recalling or rolling back a release of manufacturing server items in Altium 365 follows a structured process due to its revision control system. The Manufacture section of a managed project contains Project Releases, which include various output configurations from the project's output job files. These releases can be shared with users both inside and outside the organization via email. Because they are frozen upon release as server items under revision control, they cannot be modified or removed. If adjustments are necessary—such as changing the revision naming scheme or modifying lifecycle definitions—the best approach is to release the project as a new server item package. For users with Pro or Enterprise subscriptions, an alternative option exists: instead of deleting previous revisions, they can be hidden by changing their lifecycle status.

A365

KB: Rename a Managed Project and the local copy

This knowledge article describes how a project owner can rename an existing managed project, and how to propagate the same project name when opening the project again in Altium Designer.

A365

0

0

KB: Rename Altium 365 Workspace

If you don't like the default name given to your Altium 365 Workspace or your organization has more than one Workspace, or you want the name to better reflect it's function in your organization, the name can be changed.

A365

4

4

KB: Resolve error "You do not have a valid subscription for Altium Designer" when connecting Altium 365 workspace

I'm getting this error message: You do not have a valid subscription for Altium Designer (Expired at 1-Jan-2000). Subscription is required for Altium Designer to work with an Altium 365 Workspace."

A365

KB: Resolve ERR_TOO_MANY_REDIRECTS connecting to Workspace

Getting a message that "This Page isn't Working" and the page "redirected you too many times." ERR_TOO_MANY_REDIRECTS (Too many redirects)

A365

KB: Resolving HRID Generation Errors due to Naming Scheme Limits

This article addresses HRID generation errors in Altium Designer when releasing components to Altium 365 or Altium On-Prem Enterprise Server, or importing components via the Library Importer. It explains the causes of errors such as “Failed to get new HRID from server.” and “Failed to generate requested amount of hrids, naming scheme limit reached.”, which are typically due to restrictive or exhausted Item Naming Schemes. The article provides step-by-step solutions for adjusting naming schemes in component folders, model folders (symbols and footprints), and the Library Importer to resolve these issues.

A365

1

KB: Revert a managed server items to a previous revision in Altium 365

Managed projects, components, templates, and other items can be reverted to any previous revision committed through History page from Explorer panel, by selecting the revision to be reverted to and re-saving as the head.

A365

KB: Share project via workspaces

Is share project via workspaces an included feature for the AD20 subscription?

A365

KB: Sharing Projects to Members Outside of the Organization Without Invitation to Workspace

Managed Projects to be edited by outside users needed to be invited to workspace, but not with the new update.

A365

KB: Specify sub-folders and files within a project folder to be version controlled in Altium 365 workspace

By default, sub-folder such as "Project Outputs..." of each managed project is excluded from version control, as prescribed by .gitignore file contained inside the git repository folder.

A365

0

5

KB: Transfer workspace data

This article discusses options for migrating or synchronizing design/component data from/to an Altium 365 workspace

A365

KB: Use Folders to Manage Projects in Altium 365 Pro

With the latest release of Altium 365, projects can now be categorized by Folder Type.

A365

0

4

KB: Warnings on duplicates during library import

This article describes how the Library Importer, used to convert local libraries to managed components in an Altium 365 workspace or a managed server (Concord Pro or Nexus), handles duplicate symbols/footprints being used across multiple components with different parameters.

A365

6

0

KB: Workspace Member vs Guest vs Share with Organization

What are the differences between the different access levels to the Altium 365 workspace?