Quantcast
Channel: EPDM – The Javelin Blog
Viewing all 63 articles
Browse latest View live

SOLIDWORKS PDM Task Input Card

$
0
0

When creating or editing a SOLIDWORKS PDM Task, you can specify a Data Card that will be presented when the Task is launched.

SOLIDWORKS PDM Task Input Card

SOLIDWORKS PDM Task Input Card

When the Task is launched, a user will be presented with the specified data card.

Data Card displayed

Data Card displayed

At this point a user can enter the required information into the Data Card.

Note: The Convert and Print tasks enabled when the vault is created are not coded to use an input card and no input cards are installed. To use an input card with these tasks, create a card (or add fields to an existing card) to provide run-time values to the convert or print tasks. Use the Advanced Script Options dialog box to modify the tasks by adding code that uses the input from the card. Use the { } syntax to refer to card variables. For more information, see the Programmer’s Reference Guide, accessed by right-clicking the Add-ins feature.

The post SOLIDWORKS PDM Task Input Card appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.


SOLIDWORKS PDM Standard or Professional Upgrade Service

$
0
0

Are planning on upgrading your SOLIDWORKS PDM system? Need help to ensure the upgrade goes smoothly and downtime is kept to a minimum? Javelin’s team of Certified SOLIDWORKS PDM experts can provide your business with a comprehensive service for upgrading your SOLIDWORKS PDM Standard or Professional system from one version to the next—a maximum of two major releases back from the version that is being installed (i.e. SOLIDWORKS 2016 to SOLIDWORKS 2018).

SOLIDWORKS PDM Upgrade Service

SOLIDWORKS PDM Upgrade Service

Our SOLIDWORKS PDM Upgrade Service includes the following:

  1. Planning Meeting to confirm and validate vault configurations and versions.
  2. Initial off-site migration test on your data prior to the upgrade.
  3. Remote or On-site upgrade service.
    • Installation and upgrade of your SQL server software as required.
    • Installation and upgrade of up to three data archive servers.
    • Testing of the migrated system.
    • Installation and check on upgraded clients/users.
    • Review server log files.
    • Test PDM processes with Check in/out, Workflows, etc.
You are responsible for:
  • Ensuring that all active files are checked in by all users prior to upgrade.
  • Complete a full system backup of the Archive Servers, Archive Files and SQL database prior to upgrade.
  • Provide a copy of your PDM SQL database for off-site validation of data and process prior to the upgrade.
  • Complete installation and upgrade on remaining client computers.
  • Moving/copying data prior to site visit if the vault is being moved to new hardware for upgrade.

NOTE: Upgrading SOLIDWORKS files to the latest major release is NOT included (additional hours may be purchased for this task).

Why a SOLIDWORKS PDM Upgrade is important for your business

An upgrade to the latest SOLIDWORKS PDM system will enable your business to:

  • Ensure that you are running an optimal build and any reported issues are resolved with the latest version.
  • Support an upgraded system, if you have new hardware/software, or your system has reached the end of life (i.e. Windows Server 2003) you will need a SOLIDWORKS PDM upgrade to run on the latest system.
  • Move/transfer your PDM Vault to another server, our technicians can ensure that your downtime is kept to a minimum and your data is transferred successfully.
  • Take advantage of all the new SOLIDWORKS PDM features included with the latest version. Every new SOLIDWORKS release has hundreds of new features and performance enhancements.

Take a look at just a few of the latest features in SOLIDWORKS PDM 2018:

The benefits of a SOLIDWORKS PDM Upgrade Service from Javelin

By using the Javelin SOLIDWORKS PDM Upgrade Service you can be confident in the knowledge that your critical business system will be upgraded by an experienced Certified SOLIDWORKS PDM Professional, which means:

  • Shorter downtime: An upgrade to a major SOLIDWORKS release requires that all PDM clients are also upgraded; which will result in your users not having access to the vault until the upgrade has been completed.  We can provide an implementation plan to minimize your downtime.
  • Upgrade expertise and experience: We are familiar with the common PDM migration issues.  This knowledge allows us to provide recommendations and/or solutions to resolve your issues.
  • Comprehensive certified service: We will perform a full upgrade following SOLIDWORKS’ procedures, thus ensuring that you will not have an unsupported scenario.
  • Optimize Performance and Health-check: As part of the upgrade, we ensure all settings are in place to maximize your database performance.
  • Peace of mind: Upgrading SOLIDWORKS PDM can often seem an overwhelming process. Not all components are upgraded using the SOLIDWORKS installation manager. Having an upgrade carried out by certified experts ensures your peace of mind for your critical business system and data.

Need a SOLIDWORKS PDM upgrade?

Take the next step and contact us to find out about the latest SOLIDWORKS PDM release and our service pricing.

Contact Us

The post SOLIDWORKS PDM Standard or Professional Upgrade Service appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.

Accessing the SOLIDWORKS PDM Local Vault View from the Windows 10 Taskbar

$
0
0

Recently I was asked how to add a SOLIDWORKS PDM Vault View shortcut, to the Windows Taskbar. I was told that in previous Windows releases, this was possible. I did some research and found that this was never possible; in previous releases of Windows, but it was possible in the first preview of Windows 10.

There is a way to access the SOLIDWORKS PDM Local Vault View from the Windows 10 Taskbar, this is done by:

  1. Right-clicking on the Windows Explorer Icon, in the Windows Taskbar
  2. Then clicking on the PDM Local Vault View.
Accessing SOLIDWORKS PDM Local Vault View

File Explorer

The post Accessing the SOLIDWORKS PDM Local Vault View from the Windows 10 Taskbar appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.

Do you know that SOLIDWORKS PDM has a Search Tool?

$
0
0

Often when I’m working with SOLIDWORKS PDM users, I’ll see many navigate to files, by browsing through folders. This method is cumbersome and requires remembering in which buried sub-folder a file is stored in. These same users are often surprised to hear that SOLIDWORKS PDM include a powerful and customizable search tool.

At the top-right of the Window Explorer Vault View, there is an icon that looks like a magnifying glass, clicking on the arrow pointing down will reveal all of the searches that are available to you.

Searches

Searches

Searches can also be performed inside SOLIDWORKS (requires that PDM CAD Editor is installed), from the PDM tab, of the SOLIDWORKS Task Pane

Search from the SOLIDWORKS PDM Task Pane

Search from the SOLIDWORKS PDM Task Pane

When launching a search from SOLIDWORKS, the PDM search tool is used. In the Window Explorer Vault View, a search can be launched from within the Vault View or in a separate window, by selecting Search Tool…

Once the search is launched searches can be performed with a variety of keywords, such as File Name, State, and Checked Out By. The keywords that you can searched for are dependent on how the Search was created. Your PDM Admin should be able to provide information on the set-up of your Searches. Below, is the default Complete Search, that ships with SOLIDWORKS PDM.

Default SOLIDWORKS PDM Search

Default SOLIDWORKS PDM Search

Once the Search has found the document(s) you were looking for, you can perform many functions from the search results, such as Check-out, Open, and Change State.

The post Do you know that SOLIDWORKS PDM has a Search Tool? appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.

How to create a duplicate SOLIDWORKS PDM Vault

$
0
0

In a previous article I described how to create a Sandbox Vault. This will create a new vault with the same vault settings, but it does not copy the Database or the Archive. We can copy the Database and the Archive or parts of the archive using Collect Support Information. In this article, we will look at how to bring all those pieces together, in order to create a duplicate SOLIDWORKS PDM Vault.

The first step is create a the Sandbox Vault, making sure to select an Empty Predefined Vault. In the Sandbox Vault  article, the last step is to import the vault settings. We’ll put this off until later.

Create a duplicate SOLIDWORKS PDM Vault

Create New Vault

Once we have an empty Vault, we restore the Database through SQL Management Studio. After logging into SQL Management Studio, right-click on the Databases folder and select restore.

Restore Database

Restore Database

 

In the General tab, for Source, select Device and hit the browse button. Click on Add to select the backup that was created earlier.

Select backup devices

Select backup devices

Back in the General tab, set the Destination Database, to the Sandbox Vault.

Restore Database

Restore Database

 

Under options, select ‘Overwrite the existing database (WITH REPLACE)’ , deselect ‘Take tail-log backup before restore’ and select ‘Close existing connections to destination database’.

Overwrite the existing database (WITH REPLACE)

Overwrite the existing database (WITH REPLACE)

Next click OK to restore the vault.

Now that we have restored the production database, over top of the Sandbox database, we can copy the Archive folders, from our production vault, to our Sandbox vault. We can copy all of the archive sub-folders, but the archive folder can be massive.

Archive sub-folders

Archive sub-folders

We are likely better off to use Collect Support Information, to copy only the files and/or folders we want work with.

There are some changes that we need to make in SQL Management Studio. In Object Explorer Expand Databases>Your Sandbox database>Tables>File Tables, right click dbo.ArchiveServers and select Edit Top 200 Rows

Edit Top 200 Rows

Edit Top 200 Rows

Change the Vault Name, so that it matches that of your Sandbox vault.

Change the Vault Name

Change the Vault Name

Next, do the same for dbo.SystemInfo (also found in Databases > Your Sandbox database > Tables > File Tables)

dbo.SystemInfo

dbo.SystemInfo

To update all the SQL and PDM settings, restart SQL Server service if possible. If not, then restart PDM Database and Archive Service.

Restart Vault

Restart Vault

The last step is to import the vault settings, as described in my Sandbox Vault blog

If you experience any problems connecting to the vault, edit the Windows Registry and check that settings for Sandbox vault are correct. Ensure that everything is pointing correct locations. Below are the keys that should be checked.

HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\Vaults
HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\Vaults\ACME_Sandbox\ArchiveTable
HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\Vaults
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SolidWorks\Applications\PDMWorks Enterprise\Databases

The post How to create a duplicate SOLIDWORKS PDM Vault appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.

How are SOLIDWORKS PDM drawing properties updated?

$
0
0

In previous Javelin blogs, it was explained how to use $PRPSHEET “Write Drawing Card With Part Card Variables“.

Data Card selected variable

Data Card Variables

While this is a good tool for reducing workload, and ensuring consistency of data entry by reducing the number of data cards where information has to be entered; there is one limitation that needs to be understood. Updating the component (part or assembly card) does not update the drawing properties, until the drawing is opened in SOLIDWORKS. The reason for this, is that metadata, in the form of Custom Properties, is not written to a file until it is loaded into system memory, typically by opening the file.

The most common place where this limitation will present itself, is the Preview tab of the PDM Local View.

SOLIDWORKS PDM Preview Tab

SOLIDWORKS PDM Preview Tab

For example, if a title-block note is set to inherit a component property using $PRPSHEET.

Linked Note

Linked Note

Or if the the note is linked to a Drawing Custom Property ($PRP) this note will NOT display the correct value, until the Drawing is opened and saved.

Possible workarounds, include using the SOLIDWORKS Task Scheduler Update Files or Update Associated files, to mass update drawing files.

SOLIDWORKS Task Scheduler

SOLIDWORKS Task Scheduler

or use a custom Task, such as the one available from the SOLIDWORKS Knowledgeable, to update drawings. For Data Card Variables such as Drawn By and Drawn Date, using the ‘Default Value’, ‘Special value’, properties can be pulled from PDM to the Drawing’s Custom properties and may eliminate the need to use $PRPSHEET.

Data Card default value setting

Data Card default value setting

The post How are SOLIDWORKS PDM drawing properties updated? appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.

Moving SOLIDWORKS PDM Files does not regenerate Data Card Values?

$
0
0

When moving SOLIDWORKS PDM files between folders, with the option ‘Folder data card variable’ checked the result may not be what you are expecting.

Moving SOLIDWORKS PDM files Default Values

Default Values

 

The expectation would be that any Data Card Control, with ‘Folder data card variable’,  would pull the Variable Value from the Folder Card, regardless how the file made its way to the folder.

When a file is moved or copied and the associated Data Card has Default Values, the existing values are copied to the target file. The default values of the target file are NOT regenerated. With the exception of:

  • Data card variables with the Unique flag set. If this set, the variable value is cleared, the user is warned and the default value is regenerated.
Unique variable

Unique variable

  • Data card variable is a serial number. The user is warned and the variable value is set to next available serial number.
Serial number

Serial number

  • Default Overwrites is enabled for data card variable. The variable value for any copied file is regenerated, but the variable value is not regenerated for files that are moved (cut & paste).
Default overwrites

Default overwrites

The post Moving SOLIDWORKS PDM Files does not regenerate Data Card Values? appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.

Best Practices for using $PRPSHEET in SOLIDWORKS PDM

$
0
0

The use of $PRPSHEET can be confusing, since it can be used in more then one way and can interact with SOLIDWORKS PDM or be independent of PDM. $PRPSHEET is intended to get information from one document, such as a part or assembly, into another document, such as a drawing.

In order to understand how this transfer of information works, we need to understand the mechanism behind it. SOLIDWORKS uses metadata, to share information between documents.  Metadata, is data that describes other data. In SOLIDWORKS, metadata is referred to as Properties and a Property will have an associated Value. In the below example, we see that a part, has a Property called ‘Customer’ and this Property has a Value of ‘ACME’.

Part Property

Part Property

This Property (metadata) describes the part, as being associated with a Customer, whose name is ACME. The same Property can be used between multiple documents, but for each document, the Value will be unique.  This does not mean, that another document cannot have a Property, called Customer, whose Value is Acme. Instead each document will have a unique Property Value for Customer, called ACME. Therefore modifying the value in one document, will not affect the other. To put this in a “real world” sense, a colleague and I are both wearing ties (the Property). We can both be wearing red ties (the Value) or one of us could be wearing a blue tie and the other a red tie. If I were to change the color of tie I’m wearing, it would not effect the color of tie my colleague is wearing.

When a SOLIDWORKS Part or Assembly, has a Property, with an associated Value, I can share this Properties Value, with a Drawing. In a drawing.

For example, I want to link the Part Property ‘Customer’, to a note in my Drawing. I want to do this, so that if I change the Value of the Property ‘Customer’, in the Part. the Drawing note will update automatically. To do this, I use $PRPSHEET, to map the Part Property, to the note.

Using $PRPSHEET to Link a Part Property to a Drawing Note

Using $PRPSHEET to Link a Part Property to a Drawing Note

The advantage of linking a note to a Property, is that information is only entered and modified in one location. Thereby eliminating the chance, of mismatching information. An additional advantage is information needs to only be entered once.

SOLIDWORKS PDM also uses metadata, but in PDM, metadata is referred to as Variables. Variables act to add,  change or read information from the Vault’s Database. Like a Property, a Variable has an associated Value. The same Variable can be used in multiple documents, but for each document, the Value will be unique to given document, even the Value is the same.

As PDM users, we often interact with these Variables through a Data Card. Information entered into the Data Card, is written to the Vault’s Database and information contained in Database is displayed in the Data Card.

Variable Values Displayed in Data Card

Variable Values Displayed in Data Card

Since there are advantages to having one location to enter information (Metadata), it is good is a good practice to link the Variable Value of a document, with the document’s Property Value. This link, is defined with an PDM Attribute. In the below example, the Value for the Variable ‘Customer’, is being mapped to the SOLIDWORKS Property ‘Customer’.

Mapping Variable Value to a SOLIDWORKS Custom Property

Mapping Variable Value to a SOLIDWORKS Custom Property

In this way, when we enter a Value for the Variable ‘Customer’, in the Parts Data Card, the Value is pushed to the parts Property, ‘Customer’. If we have a note in Drawing, that is using the link $PRPSHEET:”CUSTOMER”, the Drawing note will display Value, for the Part’s Variable ‘Customer’. The flow of information from a Variable Value entered into a data card, to a Drawing note, is illustrated below.

Flow of Information from Data Card to Drawing Note

Flow of Information from Data Card to Drawing Note

Taking things a step further, I can define the mapping of a Variable, so that it’s Value, is pushed to both the Part and Drawing. By adding the attribute $PRPSHEET to Variable, we can push information, entered in the Part’s Data Card, to the Drawing’s Properties.

$PRPSHEET Attribute

$PRPSHEET Attribute

The note in my drawing, can now linked to the Drawing’s Properties, using $PRP.

The information now flows from the Data Card to the Part Properties and then to the Drawing Properties.

Flow of Information from Data Card to Drawing Properties

Flow of Information from Data Card to Drawing Properties

It is important to note, that in order for changes in the Part’s Data Card, to propagate to the Drawing’s Properties, the Drawing must first be opened and saved. If there are multiple Drawings to be updated ,SOLIDWORKS Task Scheduler’s task, ‘Update Files’ can be used.

The use of $PRPSHEET as a Variable Attribute, requires PDM add-in for SOLIDWORKS, in order the Variable Value to be mapped to the Drawing’s Properties. The  PDM add-in for SOLIDWORKS, requires a SOLIDWORKS PDM Editor license.

One final note, in this article I used a Part as an example, but this article also applies to assemblies.

The post Best Practices for using $PRPSHEET in SOLIDWORKS PDM appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.


How to update SOLIDWORKS PDM Drawings linked to the $PRPSHEET Attribute

$
0
0

In a previous article I discussed the use of $PRPSHEET to create a link between Part or Assembly Properties and a Drawing. The article described how to create the link, purely through SOLIDWORKS, and how to use SOLIDWORKS PDM to update the link.

While there are advantages to having notes in a drawing linked to Part and Assembly Properties, there is one shortcoming. In order for the links to update, the Drawing needs to be opened and saved. In this article we will look at how SOLIDWORKS Task Scheduler can be used to bulk update these Drawings.

What is SOLIDWORKS Task Scheduler?

SOLIDWORKS Task Scheduler, is a standalone application, that is used to schedule SOLIDWORKS tasks. The Update Task, will open and save documents, in SOLIDWORKS, in order to update the SOLIDWORKS files.

SOLIDWORKS Task Scheduler

SOLIDWORKS Task Scheduler

Update Files Task

This task, can be used to update Drawings, that use $PRPSHEET. These updates are required, to reflect changes made to the referenced Part or Assembly Properties.

Individual files can be updated or a folder(s) that contain files to updated, can be specified. The start date and time for the task to run needs to defined and the task can be scheduled to run daily, weekly or monthly.

Update SOLIDWORKS PDM Drawing $PRPSHEET

Update Task

For Vaulted Drawings

If the Drawings are in a PDM Vault, the following must be done, before running the Update Files task.

  • Make sure that all the drawings to be updated are checked out. Remember an entire folder can be checked. Also, PDM Searches can be used to find the Drawings, that are known to need updating.
  • In SOLIDWORKS, ensure that the SOLIDWORKS PDM Client add-in is set to be enabled at start-up.
SOLIDWORKS Add-ins

SOLIDWORKS Add-ins

The post How to update SOLIDWORKS PDM Drawings linked to the $PRPSHEET Attribute appeared first on SOLIDWORKS Tech Tips, Videos & Tutorials from Javelin.

SOLIDWORKS PDM Design Branching & Merging Overview

$
0
0

SOLIDWORKS PDM Branching and Merging, aids in the design process, by allowing the designer to Branch concepts from source file, and combine the successful concepts with the source file.

Branching

The first part of this process, is Branching. Branching creates copies of a source, in much the same way as Copy Tree, but adds the ability to maintain the History, of the branched files. By maintaining this History, the branches can later merged to their Source. Like Copy Tree, Branch is available from the Tools pull-down, in the PDM Local Vault view.

Selecting Branch from the Tools Pull-down of the Local Vault View

Selecting Branch from the Tools Pull-down of the Local Vault View

 

Many of the options available in Copy Tree, are also available from the Branch Dialogue box.

Branch Dialog Box

Branch Dialog Box

A file can be Branched multiple times and a Branch, can itself be branched. Each Branch is independent of its source file, so that any changes to a Branch or its source, will not affect other branches or the source file. The History of the Source and Branched files, will record the Branching operation.

File History Showing Branch Operation

File History Showing Branch Operation

Merging

At any time, Branched files, can be Merged with their Source file. Any modifications in the Branched file, will be carried over to the Source file. Like Branch, Merge is available from the Tools pull-down, in the PDM Local Vault view.

Selecting Merge from the Tools Pull-down of the Local Vault View

Selecting Merge from the Tools Pull-down of the Local Vault View

The dialog box for Merge is similar to both Copy Tree and Branch.

Selecting Merge from the Tools Pull-down of the Local Vault view

Selecting Merge from the Tools Pull-down of the Local Vault view

File History Showing Merge Operation

File History Showing Merge Operation

As with Branching, the Merge operation is recorded in the History of the Merged and Source files.

One final note, while the screenshots in this article showed SOLIDWORKS files, other file types, can also be branched.

The post SOLIDWORKS PDM Design Branching & Merging Overview appeared first on SOLIDWORKS Tech Tips & Tutorials.

SOLIDWORKS PDM Maintenance & Backup Recommendations

$
0
0

For SOLIDWORKS PDM Maintenance to optimize performance and prevent data loss, it is important to perform scheduled back-up of your PDM components.

Let’s first examine the components that should be backed up. These components are:

  1. The SQL Database,
  2. The Archive Folder and
  3. The Archive settings.

With the first two components, failing to back these up correctly, may lead to permanent data loss.

The first and second components, should be scheduled to occur during the same time span so there are no mismatches in data. For example, the SQL Database and the Archive Folder could be scheduled to occur over night, when no one is accessing the vault. This ensures that the information in the SQL database, matches the files in the Archive. If there are mismatches, those files may not be recoverable, if a fatal event were to occur, such as the loss of a server.

Also, back-ups should be done to a server other then where the PDM components are installed, preferably one that is in a different location.

The SQL Database

The database is typically backed up through SQL Management Studio. SQL Management Studio ships with SQL Standard or higher, and is used by PDM Professional. PDM Standard uses SQL Xpress, which does not contain SQL Management Studio, but this can be installed separately.

SQL Management Studio is installed on the database server. Once you launch this application, you will need to login with the Windows or SQL Server login.

Connect to the server

Connect to the server

Back-us of the database can be scheduled through the Maintenance tab of Object Explorer

Maintenance tab of Object Explorer

Maintenance tab of Object Explorer

To create a Back-up Plan use the Maintenance Plan Wizard,

Maintenance Plan Wizard

Maintenance Plan Wizard Tool

And schedule a Back-up.

Maintenance Plan Wizard

Maintenance Plan Wizard

If you use software to back-up your server, do not reply on it to back-up the SQL database, unless it has the purpose build functionality, to do this and you are confident in its ability to back-up databases.

The Archive Server and Settings

There are no utilities, that ship with PDM for backing up the Archive. A reliable back-up application, should be used to do this. Please note that, depending how PDM was set-up, the Archive and Database may have installed on separate servers. Also, if you a replicated environment, remember to back-up all the Archives.

The third component that should be backed up, is the Vault Settings. these settings essentially correspond to the nodes, you see in the SOLIDWORKS PDM Administration.

Back-up Vault Settings

Back-up Vault Settings

These settings are backed up from the Archive Server Configuration Tool, which is located on the Archive Server.

SOLIDWORKS PDM Archive Server

SOLIDWORKS PDM Archive Server

Backup settings, can be created for individual or groups of vaults.

Backup settings

Backup settings

SOLIDWORKS PDM Maintenance Plans

As well as backing up your data to help prevent data loss, there are a couple of Maintenance Plans, that can be configured increase database performance. SOLIDWORKS recommends running  Reorganize Index weekly and Rebuild the Index monthly. The actual frequency will depend on how much time it takes, for your SQL Index to be come fragmented. Checking the fragmentation regularly, will help you determine the scheduling

The post SOLIDWORKS PDM Maintenance & Backup Recommendations appeared first on The Javelin Blog.

How to manually update SOLIDWORKS Toolbox in a SOLIDWORKS PDM Vault

$
0
0

Before you manually update SOLIDWORKS Toolbox in SOLIDWORKS PDM Vault, first ensure there is a full recent back up of the file vault database and archive.

Next make sure that all the Toolbox parts are not checked out or in use by any currently checked out assemblies. When an existing major version Toolbox is upgraded, Toolbox parts may be need to be moved, any checked out checked out files will not be moved and could result in the update failing.

To Check whether any SOLIDWORKS Toolbox parts are currently checked out:

  • Log into a local vault view as “Admin” and use the search tool to make sure no files are checked out under the Toolbox folder in the vault.
  • To find if any Toolbox parts are used by checked out assemblies, run the SolidWorks Enterprise PDM report “ListAllCheckedOutParentsWithToolboxParts.crp. This report can be downloaded from the SolidWorks Knowledgebase article S-058099. Knowledgebase articles are accessible from the SolidWorks Customer Portal (www.solidworks.com)

    Report Generator

    Report Generator

  • Check in all assemblies that are listed in the results area of the report.

To manually upgrade Toolbox:

  1. Ensure that no one is accessing Toolbox during this process.
  2. Log into a vault view as ‘Admin’
  3. Check-out the entire Toolbox folder typically “SOLIDWORKS Data” folder
  4. Browse to SOLIDWORKS 2019 installation folder, typically “C:\Program Files\SOLIDWORKS Corp\SOLIDWORKS“, and then to “Toolbox\data utilities” right click on “UpdateBrowserDatabase.exe” and select “Run as administrator”.

    Update Browser Database

  5. Click the “…” button to browse for the file “swbrowser.sldedb” located in the PDM Vault typically “SOLIDWORKS Data\lang\english“.
  6. To begin the upgrade, click the “Update” button.

    Update Toolbox Database

  7. Confirm the Toolbox update was successful by repeating Step 4 and Step 5. The Database version should match the Update Version when the update is complete.
  8. Once the update is complete, start-up SOLIDWORKS and ensure that the correct path for the updated Toolbox is specified in Tools > Options > System Options > Hole Wizard /Toolbox.
  9. Check-in the updated Toolbox folder
  10. Select the top level Toolbox folder, click on Tools > Clear Local Cache

    Clear Local Cache

  11. Select the SOLIDWORKS Data folder, click on Get Latest Version (or right click on SOLIDWORKS Data folder and select Get Latest Version from right click menu.)

    Get Latest Version

Upgrading the remainder of the client computers:

  • Log in as a user that has at least read permission to the Toolbox folder on other client machines.
  • Repeat Step 10 and Step 11.

The post How to manually update SOLIDWORKS Toolbox in a SOLIDWORKS PDM Vault appeared first on The Javelin Blog.

How to use the SOLIDWORKS PDM View Setup Tool

$
0
0

Once the SOLIDWORKS PDM Client software is installed the next step is to setup the Vault View which give the user(s) access to the vault through Windows Explorer. The easiest way to do this is by using the SOLIDWORKS PDM View Setup tool.  It is recommended that you perform this procedure with full Administrator privileges.

SOLIDWORKS PDM View Setup Tool Step-by-step guide

The View Setup is found by going to the Start Menu > SOLIDWORKS PDM > View Setup.

SOLIDWORKS PDM View Setup

SOLIDWORKS PDM View Setup

Screen 1:  Welcome

Launch the program then click “Next>“.

Welcome dialog

Welcome dialog

Screen 2:  Select Servers

On the Select servers screen you will see any Archive Servers that your system can currently communicate with across the network.  If you are in a replicated environment make sure that you select the Archive Server that is local to your office (you may need to confirm this with your PDM Administrator to make sure which server is the one in your office).  Check the box beside the Archive Server and click “Next>“.

Select Servers

Select Servers

If you do not see your Archive Server, it’s possible that the broadcast which identifies the Archive Server and adds it to this list may be blocked.  That’s ok, you can still manually attach to the Archive server by clicking “Add…” and typing in the Computer Name directly.

If you still cannot connect to the Archive Server it’s possible that either there is a network connection issue or a firewall is blocking the port (by default the Archive Server communicates across port 3030).

Connected Server

Connected Server

Screen 3:  Select Vaults

On the Select vaults screen you will see a list of Vaults that are available on the Archive Server that you selected in the last screen.  Check the box beside the Vault or Vaults that you wish to attach to, then click “Next>“.

If you receive a Status other than “Ok” when selecting the vault to attach, you may have existing vault view information in the registry.  This can be cleaned up through the Registry Editor.

Select Vaults

Select Vaults

Screen 4:  Select Location

On the Select location screen you can specify where you want the vault folder to be located and who should have access to it.  It is important that the location where the Vault View is placed is a folder where the Windows user will have full permissions.  The Vault View is built on top of a regular Windows folder, so it’s essential that the user have all the normal permissions and access.

Under “Attach type” you can select who will have access to the Vault View.  Unless there is a specific need to have the vault folder be only accessible to a specific user (for instance if the workstation is shared between multiple users) it is best to use the default “For all users on this computer”.  Once you have selected the Location and the Type, click “Next>“.

Select Location

Select Location

Screen 5:  Finish

Once you’re ready click “Finish” to complete the process of adding the Vault View as you specified in the last screen.

Finish Process

Finish Process

SOLIDWORKS PDM view setup complete

SOLIDWORKS PDM view setup complete

SOLIDWORKS PDM view setup Completion

The vault view will be created in the folder that you specified in Screen 4.  As soon as the view is created you will see the contents of the vault (that you have permission to see), even though those files will not be local on your system until you access them.

 

The post How to use the SOLIDWORKS PDM View Setup Tool appeared first on The Javelin Blog.

SOLIDWORKS PDM Vault View Grey Folder and Local Files

$
0
0

A SOLIDWORKS PDM folder or file showing up in a grey colour indicates that a local folder or local file existed in your local file vault view, but not in the PDM vault itself.

SOLIDWORKS PDM Grey Folder and File

Local files and folders are displayed in a vault view

When you browse through folders and work with files in the vault view, SOLIDWORKS PDM will retrieve and cache the copies of the folders and files locally. These local copies will remain in the cache, even when you log out of the vault view. So that next time you access the folder or file SOLIDWORKS PDM will not have to retrieve the files again.

Why would a file or folder be coloured grey?

If you have a cached copy of a file or folder, that is no longer accessible in the vault itself, it will show up in grey colour to indicate it is only stored locally. There are several reasons you may see these local files or folders, and it is in most cases normal that they appear:

  1. You log into the vault view where a different user with more access permissions previously cached a file, but the current user does not have read permissions to the folders or files. The previously cached objects would still be in the view.
  2. The folder or file has been deleted, renamed or moved, and the previously cached copy remains.
  3. The files were added to the local view by an application, but were not added to the vault itself – therefore only existing locally. (Note that some files should remain local, such as temporary files created by applications).

Clear Local Cache

If you wish to remove the local copy of files, you have worked with and no longer need to have it cached locally, use the ‘Clear Local Cache’ command or remove local copy in dialog (note that it will only process files part of the vault, and local folders are not removed).

Clear Local Cache

Clear Local Cache

Hiding Local Files

If you wish to not see the local files or folders, right-clickUsers’ in Administration tool, select ‘Settings’ > ‘Explorer’ tab and enable ‘Show only files that are part of the file vault’.

Settings dialog controlling how local files or folders should be handled

Settings dialog controlling how local files or folders should be handled

Automatic Removal of Local Files

If you wish to have local copies of deleted, moved or renamed files and folder automatically removed, enable the ‘Local file clean-up’ option in the settings dialog. Note that if the object is still in the vault in same location, and you log in as user with less permission, the local copy will not be cleared.

NOTE that if the folders or files show up in a grey colour you will NOT be able to do any vault operations on the objects (besides add to vault) – if they should not be local, verify that you have sufficient folder and workflow permission to see the objects.

The post SOLIDWORKS PDM Vault View Grey Folder and Local Files appeared first on The Javelin Blog.

SOLIDWORKS PDM Archive Server could not open the Windows Registry?

$
0
0

After installing the SOLIDWORKS PDM Client for the first time, the Archive Server must be identified in PDM Administration.

Addin Server to Client Computer

When attaching a client computer to an Archive Server, the logged-in User’s Profile is compared to the ‘Attach access’ and ‘Administrative access’ of the user profile. If the user profile credentials cannot be matched, the user will be prompted to log into the PDM Archive Server.

Login Archive Server

Archive Server error

In some cases this process may fail, with the error ‘The Archive Server could not open the Windows Registry’

The Archive Server could not open the Windows Registry

There can be other associated errors, which I have listed below:

  • Could not initialize archive serve connection. Error Description: The system detected a possible attempt to
    compromise security.
  • No authority could be contacted for authentication.
  • No credentials are available in the security package.
  • Could not authenticate with server.
  • The specified Archive Server operation was invalid in this context.
  • The Archive Server could not open the Windows Registry.
  • The function requested is not supported.

Why does this error occur?

This issue can also occur when creating a local vault view or when attempting to ‘Refresh’ the vault in PDM Administration.

Refresh Vault

This error will often occur, on client computers that are disconnected from their company’s domain. The problem stems from the domain controller not responding when the client sends the Windows domain profile credentials for authentication. This problem can also occur if a user is logged in using Windows via an Azure Active Directory account. The issue can also occur when PDM is installed using a local machine user profile, and unable to create a vault using a domain network account.

Solving the registry access error

Possible solutions include:

  • Run the administration tool or view setup wizard with a different Windows user account.
    • Browse to the SOLIDWORKS PDM installation folder
    • Hold down the ‘SHIFT’ key and right-click the application to run ConisioAdmin.exe’ for attaching the Archive Server or ViewSetup.exe’ to create a local vault view.
    •  Select ‘Run as different user’.

Run as Different User

    • Use a different local Windows account and enter the local system name using the format ‘SYSTEM_Name\USER_Name’.

Run as Different User

  • Create a temporary Windows user that is part of the local administrator group. While logged in as this temporary Windows user, attach the vault or create the local vault view. The vault and vault view should now be accessible when logged into the domain.

Need help with your SOLIDWORKS PDM?

Javelin’s team of Certified Experts provide a variety of SOLIDWORKS PDM Services including System Implementation, Health Check Optimization and Upgrades. Learn more about our PDM services »

The post SOLIDWORKS PDM Archive Server could not open the Windows Registry? appeared first on The Javelin Blog.


How are SOLIDWORKS PDM drawing properties updated?

$
0
0

In previous Javelin blogs, it was explained how to use $PRPSHEET “Write Drawing Card With Part Card Variables“.

Data Card selected variable

Data Card Variables

While this is a good tool for reducing workload, and ensuring consistency of data entry by reducing the number of data cards where information has to be entered; there is one limitation that needs to be understood. Updating the component (part or assembly card) does not update the drawing properties, until the drawing is opened in SOLIDWORKS. The reason for this, is that metadata, in the form of Custom Properties, is not written to a file until it is loaded into system memory, typically by opening the file.

The most common place where this limitation will present itself, is the Preview tab of the PDM Local View.

SOLIDWORKS PDM Preview Tab

SOLIDWORKS PDM Preview Tab

For example, if a title-block note is set to inherit a component property using $PRPSHEET.

Linked Note

Linked Note

Or if the the note is linked to a Drawing Custom Property ($PRP) this note will NOT display the correct value, until the Drawing is opened and saved.

Possible workarounds, include using the SOLIDWORKS Task Scheduler Update Files or Update Associated files, to mass update drawing files.

SOLIDWORKS Task Scheduler

SOLIDWORKS Task Scheduler

or use a custom Task, such as the one available from the SOLIDWORKS Knowledgeable, to update drawings. For Data Card Variables such as Drawn By and Drawn Date, using the ‘Default Value’, ‘Special value’, properties can be pulled from PDM to the Drawing’s Custom properties and may eliminate the need to use $PRPSHEET.

Data Card default value setting

Data Card default value setting

The post How are SOLIDWORKS PDM drawing properties updated? appeared first on The Javelin Blog.

Moving SOLIDWORKS PDM Files does not regenerate Data Card Values?

$
0
0

When moving SOLIDWORKS PDM files between folders, with the option ‘Folder data card variable’ checked the result may not be what you are expecting.

Moving SOLIDWORKS PDM files Default Values

Default Values

 

The expectation would be that any Data Card Control, with ‘Folder data card variable’,  would pull the Variable Value from the Folder Card, regardless how the file made its way to the folder.

When a file is moved or copied and the associated Data Card has Default Values, the existing values are copied to the target file. The default values of the target file are NOT regenerated. With the exception of:

  • Data card variables with the Unique flag set. If this set, the variable value is cleared, the user is warned and the default value is regenerated.
Unique variable

Unique variable

  • Data card variable is a serial number. The user is warned and the variable value is set to next available serial number.
Serial number

Serial number

  • Default Overwrites is enabled for data card variable. The variable value for any copied file is regenerated, but the variable value is not regenerated for files that are moved (cut & paste).
Default overwrites

Default overwrites

The post Moving SOLIDWORKS PDM Files does not regenerate Data Card Values? appeared first on The Javelin Blog.

Best Practices for using $PRPSHEET in SOLIDWORKS PDM

$
0
0

The use of $PRPSHEET can be confusing, since it can be used in more then one way and can interact with SOLIDWORKS PDM or be independent of PDM. $PRPSHEET is intended to get information from one document, such as a part or assembly, into another document, such as a drawing.

In order to understand how this transfer of information works, we need to understand the mechanism behind it. SOLIDWORKS uses metadata, to share information between documents.  Metadata, is data that describes other data. In SOLIDWORKS, metadata is referred to as Properties and a Property will have an associated Value. In the below example, we see that a part, has a Property called ‘Customer’ and this Property has a Value of ‘ACME’.

Part Property

Part Property

This Property (metadata) describes the part, as being associated with a Customer, whose name is ACME. The same Property can be used between multiple documents, but for each document, the Value will be unique.  This does not mean, that another document cannot have a Property, called Customer, whose Value is Acme. Instead each document will have a unique Property Value for Customer, called ACME. Therefore modifying the value in one document, will not affect the other. To put this in a “real world” sense, a colleague and I are both wearing ties (the Property). We can both be wearing red ties (the Value) or one of us could be wearing a blue tie and the other a red tie. If I were to change the color of tie I’m wearing, it would not effect the color of tie my colleague is wearing.

When a SOLIDWORKS Part or Assembly, has a Property, with an associated Value, I can share this Properties Value, with a Drawing. In a drawing.

For example, I want to link the Part Property ‘Customer’, to a note in my Drawing. I want to do this, so that if I change the Value of the Property ‘Customer’, in the Part. the Drawing note will update automatically. To do this, I use $PRPSHEET, to map the Part Property, to the note.

Using $PRPSHEET to Link a Part Property to a Drawing Note

Using $PRPSHEET to Link a Part Property to a Drawing Note

The advantage of linking a note to a Property, is that information is only entered and modified in one location. Thereby eliminating the chance, of mismatching information. An additional advantage is information needs to only be entered once.

SOLIDWORKS PDM also uses metadata, but in PDM, metadata is referred to as Variables. Variables act to add,  change or read information from the Vault’s Database. Like a Property, a Variable has an associated Value. The same Variable can be used in multiple documents, but for each document, the Value will be unique to given document, even the Value is the same.

As PDM users, we often interact with these Variables through a Data Card. Information entered into the Data Card, is written to the Vault’s Database and information contained in Database is displayed in the Data Card.

Variable Values Displayed in Data Card

Variable Values Displayed in Data Card

Since there are advantages to having one location to enter information (Metadata), it is good is a good practice to link the Variable Value of a document, with the document’s Property Value. This link, is defined with an PDM Attribute. In the below example, the Value for the Variable ‘Customer’, is being mapped to the SOLIDWORKS Property ‘Customer’.

Mapping Variable Value to a SOLIDWORKS Custom Property

Mapping Variable Value to a SOLIDWORKS Custom Property

In this way, when we enter a Value for the Variable ‘Customer’, in the Parts Data Card, the Value is pushed to the parts Property, ‘Customer’. If we have a note in Drawing, that is using the link $PRPSHEET:”CUSTOMER”, the Drawing note will display Value, for the Part’s Variable ‘Customer’. The flow of information from a Variable Value entered into a data card, to a Drawing note, is illustrated below.

Flow of Information from Data Card to Drawing Note

Flow of Information from Data Card to Drawing Note

Taking things a step further, I can define the mapping of a Variable, so that it’s Value, is pushed to both the Part and Drawing. By adding the attribute $PRPSHEET to Variable, we can push information, entered in the Part’s Data Card, to the Drawing’s Properties.

$PRPSHEET Attribute

$PRPSHEET Attribute

The note in my drawing, can now linked to the Drawing’s Properties, using $PRP.

The information now flows from the Data Card to the Part Properties and then to the Drawing Properties.

Flow of Information from Data Card to Drawing Properties

Flow of Information from Data Card to Drawing Properties

It is important to note, that in order for changes in the Part’s Data Card, to propagate to the Drawing’s Properties, the Drawing must first be opened and saved. If there are multiple Drawings to be updated ,SOLIDWORKS Task Scheduler’s task, ‘Update Files’ can be used.

The use of $PRPSHEET as a Variable Attribute, requires PDM add-in for SOLIDWORKS, in order the Variable Value to be mapped to the Drawing’s Properties. The  PDM add-in for SOLIDWORKS, requires a SOLIDWORKS PDM Editor license.

One final note, in this article I used a Part as an example, but this article also applies to assemblies.

The post Best Practices for using $PRPSHEET in SOLIDWORKS PDM appeared first on The Javelin Blog.

How to update SOLIDWORKS PDM Drawings linked to the $PRPSHEET Attribute

$
0
0

In a previous article I discussed the use of $PRPSHEET to create a link between Part or Assembly Properties and a Drawing. The article described how to create the link, purely through SOLIDWORKS, and how to use SOLIDWORKS PDM to update the link.

While there are advantages to having notes in a drawing linked to Part and Assembly Properties, there is one shortcoming. In order for the links to update, the Drawing needs to be opened and saved. In this article we will look at how SOLIDWORKS Task Scheduler can be used to bulk update these Drawings.

What is SOLIDWORKS Task Scheduler?

SOLIDWORKS Task Scheduler, is a standalone application, that is used to schedule SOLIDWORKS tasks. The Update Task, will open and save documents, in SOLIDWORKS, in order to update the SOLIDWORKS files.

SOLIDWORKS Task Scheduler

SOLIDWORKS Task Scheduler

Update Files Task

This task, can be used to update Drawings, that use $PRPSHEET. These updates are required, to reflect changes made to the referenced Part or Assembly Properties.

Individual files can be updated or a folder(s) that contain files to updated, can be specified. The start date and time for the task to run needs to defined and the task can be scheduled to run daily, weekly or monthly.

Update SOLIDWORKS PDM Drawing $PRPSHEET

Update Task

For Vaulted Drawings

If the Drawings are in a PDM Vault, the following must be done, before running the Update Files task.

  • Make sure that all the drawings to be updated are checked out. Remember an entire folder can be checked. Also, PDM Searches can be used to find the Drawings, that are known to need updating.
  • In SOLIDWORKS, ensure that the SOLIDWORKS PDM Client add-in is set to be enabled at start-up.
SOLIDWORKS Add-ins

SOLIDWORKS Add-ins

The post How to update SOLIDWORKS PDM Drawings linked to the $PRPSHEET Attribute appeared first on The Javelin Blog.

SOLIDWORKS PDM Design Branching & Merging Overview

$
0
0

SOLIDWORKS PDM Branching and Merging, aids in the design process, by allowing the designer to Branch concepts from source file, and combine the successful concepts with the source file.

Branching

The first part of this process, is Branching. Branching creates copies of a source, in much the same way as Copy Tree, but adds the ability to maintain the History, of the branched files. By maintaining this History, the branches can later merged to their Source. Like Copy Tree, Branch is available from the Tools pull-down, in the PDM Local Vault view.

Selecting Branch from the Tools Pull-down of the Local Vault View

Selecting Branch from the Tools Pull-down of the Local Vault View

 

Many of the options available in Copy Tree, are also available from the Branch Dialogue box.

Branch Dialog Box

Branch Dialog Box

A file can be Branched multiple times and a Branch, can itself be branched. Each Branch is independent of its source file, so that any changes to a Branch or its source, will not affect other branches or the source file. The History of the Source and Branched files, will record the Branching operation.

File History Showing Branch Operation

File History Showing Branch Operation

Merging

At any time, Branched files, can be Merged with their Source file. Any modifications in the Branched file, will be carried over to the Source file. Like Branch, Merge is available from the Tools pull-down, in the PDM Local Vault view.

Selecting Merge from the Tools Pull-down of the Local Vault View

Selecting Merge from the Tools Pull-down of the Local Vault View

The dialog box for Merge is similar to both Copy Tree and Branch.

Selecting Merge from the Tools Pull-down of the Local Vault view

Selecting Merge from the Tools Pull-down of the Local Vault view

File History Showing Merge Operation

File History Showing Merge Operation

As with Branching, the Merge operation is recorded in the History of the Merged and Source files.

One final note, while the screenshots in this article showed SOLIDWORKS files, other file types, can also be branched.

The post SOLIDWORKS PDM Design Branching & Merging Overview appeared first on The Javelin Blog.

Viewing all 63 articles
Browse latest View live