Connector For SOLIDWORKS Performance Issues

This issue was discovered in a customer environment that has 3DEXPERIENCE 2016X with FP1711. We had a SOLIDWORKS Connector client that had major performance issues. Within the connector explorer interface, if we click on Actions or right-click on a non-cached object, it was taking 45+ seconds for the menu to display. After the object was cached by selecting “Get Latest Iteration”, there was no problem. Solution : WINRAR was the root cause of the issue. Looks like it was trying to cache or read the objects before 3DEXP software. Uninstalling WINRAR solved the issue and the performance was back to normal.

How to Avoid Selecting ENOVIA Installer Path for Web Applications

After installing the Platform applications, we need to select the ENOVIA installer path for all web applications. With so many web applications to install, this can become a boring and time consuming task to perform especially when this operation needs to be done twice. Once for the GA and again for the fix pack install. There is an easier option to solve this issue by entering the path for the installer in the Windows environment variable. Extract the Installer from Platform install folder. Open Windows system environment variables Click New under System variables Create variable name “DSY_ENOVIA_Installer” and enter the path in the variable value Click OK to close the […]

SOLIDWORKS: Filtering Configurations with Enovia 2016X

SOLIDWORKS configurations play a huge role in the way that many companies use the software. When it some to configurations, some companies will choose to use each configuration as a separate part number, while others choose to use the “one file, one part” methodology. No matter which method is in use in you company, you are most likely using configurations in some way, shape, or form. Even users that don’t consider configs as separate parts will most likely use them for simplified representation, alternate position, or one of the other thousands of uses. If your still telling yourself that you don’t use configurations at all, go ahead and create a sheet metal […]

What’s New in ENOVIA 2017X Platform

ENOVIA 2017X Platform – What’s New Apart from the standard platform components that were part of 2016x (3DSPACE, FED SEARCH, FTS, 3DPASSPORT, 3DDASHBOARD etc.), two new components have been introduced in 2017x. 3DComment Provides the ability for 3DEXPERIENCE platform members to interact with one another by liking content and adding comments to any item in the system. This is a mandatory module that needs to be installed. 3DNotification Helps 3DEXPERIENCE platform members get timely updates about activities going on. It basically controls the notification message services. This is a optional module. Azeem Saied InFlow Technology

SOLIDWORKS PDM One Click Open Files

Recently with all of the Windows upgrades we have been receiving support calls regarding why some/all files are opening from the vault with one click. Although this is not a PDM setting but rather a Windows one, we thought we would share the most common solution to this issue. Below are a few screen shots of there that setting in windows is and how to correct it for the entire vault. To begin, below is a screenshot of my local vault (at the root, this is an important step) with the Organize menu displayed in the top left corner. Here you will select "Change folder and search options". Here, on […]

Java Memory Usage for SOLIDWORKS Connector

On SOLIDWORKS V6 clients, the JAVA options are read from the IEF client config.xml file. You could experience performance issues and errors during check-in or major resource intensive operations like undo-check-out of a large assembly if these parameters are not set. Go to C:\Program Files\Dassault Systemes\IEFClientV6R2014X\IEFClientWorkspaceServices\ and open config.xml using notepad. Overwrite the <javaoptions> string with the following and add <slwjavaoptions>.. string below it. <javaoptions>-Xmx8192m -Xms4096m</javaoptions> <slwjavaoptions>-Xss512k -Xmx8192m -Xms4096m -XX:SurvivorRatio=2 -XX:NewSize=2048m -XX:MaxNewSize=4096m -XX:MaxPermSize=2048m -XX:+DisableExplicitGC -XX:+UseCompressedOops</slwjavaoptions> Note: Xmx is the maximum heap and Xms is the initial heap startup parameter. In the example above, Java will use 8GB max and 4GB initial. These values could vary depending on the RAM you have. […]

InFlow participates in the ENOVIA SOLIDWORKS event in Chicago

For those who missed it, InFlow Technology presented at the first ENOVIA 3DEXPERIENCE for SOLIDWORKS users event this week in Chicago.  Attendees were able to see the ENOVIA SOLIDWORKS integration and see how ENOVIA could be tied together with an existing EPDM environment.  My presentation covered Migration Strategies for ENOVIA. The presentations are available on the Dassault swym site.  Visit https://swym.3ds.com/#post:39476 to see the information.  If you do not have access to the site, you can request a login and then join the community called: Collaborative Innovation: Powered by ENOVIA.  On this same site, you can request my presentation at https://swym.3ds.com/#media:113847.  Enjoy the presentations and other pictures available on the site.  If […]

Automatic EBOM Sync Functionality

How to run EBOM Sync automatically on check-in of SOLIDWORKS objects? Running EBOM sync on every SOLIDWORKS object that is checked-in to ENOVIA can be a time consuming task. With the following steps, EBOM sync will be executed automatically as soon as the SOLIDWORKS object is checked-in. 1. On the ENOVIA server, start Matrix. 2. Login as creator. 3. Search: Type – "SWNewArch_R216.HF2" [Note: make sure the correct GCO is selected] 4. Right click – Properties – Attributes 5. Set the value of "IEF-EBOMSynchOnDesignCreation" to "TRUE"

Adding Additional Columns in Windows Explorer

For users of SOLIDWORKS Connector, a bug in the ENOVIA system (R2014X FP1530) prevents users from accessing ENOVIA if the default columns in explorer are modified. This option is normally accessed by right-clicking the columns section as seen in example screenshot below. The workaround is to delete the user LCO object. This bug has been fixed in FP1538.