Best Practice Information

Domain and Role/Product

SOLIDWORKS Design  Collaborative Designer for SOLIDWORKS SOLIDWORKS Design with Cloud Services 

What's covered? Jump to each section using the Contents List in the top right!

• Understanding File Properties
• Understanding Attributes
• Planning
• Data Type Mapping
• Content Type Mapping
• Create Custom Attributes
• Configure Attribute Mapping
• Attribute Mapping in Use
• Limitations, Tips, and Troubleshooting
• Frequently Asked Questions

Revision History

Note
All SolidPractices are written as guidelines. It is a strong recommendation to use these documents only after properly evaluating your requirements. Distribution of this document is limited to Dassault Systèmes SolidWorks employees, VARs, and customers that are on active subscription. You may not post this document on blogs or any internal or external forums without prior written authorization from Dassault Systèmes SolidWorks Corporation.
This document was updated using 3DEXPERIENCE platform SaaS R2026x FD01 and SOLIDWORKS® Design 2026 SP01. 
If you have questions or need assistance in understanding the content, please get in touch with your SOLIDWORKS Partner.

Your Feedback Requested
We would like to hear your feedback and suggestions for new topics. After reviewing this document, please take a few minutes to fill out a brief survey. Your feedback will help us create the content that directly addresses your challenges.

1) Preface

When a company creates content, it often creates additional information to help define the content. The additional information is specific to the company, and it can be an essential piece of communication for stakeholders inside and outside the company.

This document discusses that topic within the context of SOLIDWORKS Design and two operating systems or platforms, Windows® and 3DEXPERIENCE platform SaaS. SOLIDWORKS Design is an app that is common to both platforms.

Members of an engineering department use SOLIDWORKS Design to create content. The additional information that they create can be Windows file properties or SOLIDWORKS Design file properties.

Members of a company use various apps in the 3DEXPERIENCE platform to create content. The additional information that they create is 3DEXPERIENCE platform attributes.

Attributes are the common language for all platform members, regardless of department. Because of this, defining attributes is one of the first tasks a platform administrator performs when configuring their platform for first use.

To ensure that the additional information is accurate in both platforms, follow these best practices to create a mapping between the two.

2) Understanding File Properties

a) Windows File Properties

Several Windows file properties are available for use in SOLIDWORKS Design. You access these file properties in the Summary tab of the Properties dialog box.

These file properties are unique to Windows. You cannot map them to 3DEXPERIENCE platform attributes.

b) SOLIDWORKS Design File Properties

i) Content Types

SOLIDWORKS Design has six content types for which you can create file properties:

• Part
  • Weldment with structural member profile
  • Weldment without structural member profile
  • Sheet Metal
• Assembly
• Drawing
   

ii) Property Types

Within the six content types, you can create up to three classifications of file properties:

• Custom
• Configuration
• Cut List

Custom properties apply to all configurations of a part or assembly file. Configuration properties apply to a specific part or assembly configuration. Cut list properties apply to a specific cut list item. You access file properties in the Properties and Cut-List Properties dialog boxes.

Custom, configuration, and cut list properties are unique to SOLIDWORKS Design, and it is possible to map them to 3DEXPERIENCE attributes.

SOLIDWORKS Design provides predefined lists of common properties. One list applies to custom and configuration properties. The other list applies to cut list properties. You can edit both lists to suit the needs of your company or ignore these properties and enter custom names.

1. PLM Attributes

When the 3DEXPERIENCE add-in is active, several types of PLM Attributes (or 3DEXPERIENCE attributes) are available at the bottom of the list. Similar to the \\\$PRP syntax for SOLIDWORKS Design file properties, PLM Attributes use a \\\$PLMPRP syntax. 

You cannot remove attributes from these lists. PLM Attributes are designed to be Although it is not a best practice, custom attributes display in the PLM Attributes list when mapped from 3DEXPERIENCE to SOLIDWORKS Design or bidirectionally. See section 8 for more information.
 

iii) Data Types

For custom and configuration properties, there are five types of data to choose from:

iv) 3DEXPERIENCE Integration

Unlike SOLIDWORKS Design, the 3DEXPERIENCE platform only has one classification of attributes. To make SOLIDWORKS Design have one classification of properties, you can activate the Update SOLIDWORKS files for compatibility with the 3DEXPERIENCE platform option. 

When you update files, the system disables custom properties (for part and assembly content types) and moves them to configuration properties. With one classification of file properties per content type, files are optimized for compatibility with the 3DEXPERIENCE platform. 

PLM Attributes are available with and without updating.

It is a best practice to update new SOLIDWORKS Design files for compatibility with the 3DEXPERIENCE platform. 

See the SolidPractices titled “Using SOLIDWORKS Configurations with the 3DEXPERIENCE Platform" for more information on these options. Make sure to review this document if you are moving legacy data to the 3DEXPERIENCE platform.

3) Understanding Attributes

a) Default Attributes

Several default attributes are available in the 3DEXPERIENCE platform. These attributes are comparable to the Windows file properties from section 2a. They are available for use in SOLIDWORKS Design like Windows file properties are.

There are many ways to access and view attributes. In SOLIDWORKS Design, as explained in the previous section, you can add them as file properties. In the 3DEXPERIENCE platform, a common way to access the attributes is opening the Information web app or side panel.

b) Custom Attributes

Unlike SOLIDWORKS Design, the 3DEXPERIENCE platform does not provide a list of common attributes for content types. If you want other attributes, then you must create them for each content type. The attributes you create are called custom attributes. Custom attributes are to the 3DEXPERIENCE platform as file properties are to SOLIDWORKS Design.

i) Content Types

3DEXPERIENCE platform SaaS has 591 content types for which you can create custom attributes. Of these, only six apply to SOLIDWORKS Design data:

• CAD Family

NOTE: The ability to map custom properties for part and assembly content types became unavailable in R2026x FD01 (February 2026). If your 3DEXPERIENCE subscription started before that date, then you can map custom properties to CAD Family. However, it is not a best practice. 

The best practice is only to map configuration properties for part and assembly content types.

• Drawing
• Physical Product
• SW Generic Member
• SW Sheet Metal Member
• SW Structural Member 

1. SOLIDWORKS Design Data Model

As documented in Knowledge Base article QA00000070398, when you save SOLIDWORKS Design files to 3DEXPERIENCE, the platform converts the files into 3DEXPERIENCE content types.

• For parts, the platform hierarchically creates:
   
  • CAD Family (which represents the part file)
    • Physical Product (for each configuration in the part)
      • 3D Shape (for each Physical Product)
         
• For weldment parts, with profiles, with published cut-list items, the platform hierarchically creates:
   
  • CAD Family
    • Physical Product
      • 3D Shape
      • SW Structural Member 
         
• For weldment parts, without profiles, with published cut-list items, the platform hierarchically creates:
   
  • CAD Family
    • Physical Product
      • 3D Shape
      • SW Generic Member 
         
• For sheet metal parts, without profiles, with published cut-list items, the platform hierarchically creates:
   
  • CAD Family
    • Physical Product
      • 3D Shape
      • SW Sheet Metal Member 
         
• For assemblies, the platform hierarchically creates:
   
  • CAD Family (which represents the assembly file)
    • Physical Product (for each configuration in the assembly)
    • Embedded Physical Product (for each virtual part)
       
• For drawings, the platform creates a Drawing.
   

ii) Data Types

For custom attributes, there are eight types of data to choose from:

Each data type has rules that you must follow. See section 7 for more information on some of the other parameters.

c) Other Attributes

The 3DEXPERIENCE platform has several other types of attributes. The user interface does not identify or distinguish between the other types. However, it is useful to know that other types exist in cases where you are identifying the cause of a problem. The PLM Attributes include many other types.

4) Planning

• Only a platform administrator can add attributes.
• To avoid scenarios where data has missing values, it is a best practice only to add custom attributes before you create content in a collaborative space.

The platform reinforces this best practice when you create or delete custom attributes.

• If you add custom attributes after you create content in a collaborative space, then
  • Add the custom attributes after working hours or when no platform members are creating or modifying content.
  • Follow the instructions in section 7 to propagate the attributes.
  • Notify your platform members that there are new custom attributes.
  • Explain to your platform members that they must edit and resave SOLIDWORKS Design files to synchronize the data with the new custom attributes.
• Moving or migrating legacy files to your platform requires intimate knowledge of the file property methodologies in those files. That knowledge, plus the knowledge of content types and data types, provides the foundation to determine what custom attributes to create.

• Expect to change your file property methodology to accommodate the requirements of 3DEXPERIENCE platform SaaS. You can use the Custom Properties Manager tool in Knowledge Base article QA00000109506 to aide in this process. Changes could include:

  • Deleting custom or configuration properties from parts and assemblies.
  • Copying custom properties to configuration properties.
  • Changing data types.
  • Updating or changing property templates if you use the Property Tab Builder and Custom Properties task pane to enter file properties.

   

a) File Preparation Assistant

Use the Mismatched custom property check in the File Preparation Assistant tool to identify data type mapping conflicts.

5) Data Type Mapping

• You can map any property to any String attribute. To avoid mapping problems, particularly with file properties that have the Date data type, you can choose only to create String custom attributes.
   
• File properties with a Yes value are equivalent to custom attributes with a True value. File properties with a No value are equivalent to custom attributes with a False value.
   
• It is possible to map file properties that have a Number date type to custom attributes that have an Integer data type, even if the property value is not an integer. However, the best practice is to map Number to Real. Examples:
  • ‘1.’ is not an integer. If a property with this value maps to an Integer attribute, then it evaluates as ‘1’.
  • ‘1.57’ is not an integer. If a property with this value maps to an Integer attribute, then it evaluates as ‘1’. In both cases, the platform does not round the value.
     

• You can only map file properties that have an Equation data type from SOLIDWORKS Design to 3DEXPERIENCE, and it is a best practice to create the mapped attribute as Read-Only.

  • In this scenario, regardless of the unit system in the file, the Meter, Kilogram, Second (MKS) value of the property displays shows in the 3DEXPERIENCE attribute.
  • The only supported Dimensions (Unit) are length, mass, angle, or any combination of these three, like area, volume, or density.
  • The only supported content types for this data type mapping are Physical Product and Drawing.

   

6) Content Type Mapping

NOTE: The ability to map custom properties for part and assembly content types became unavailable in R2026x FD01 (February 2026). If your 3DEXPERIENCE subscription started before that date, then you can map custom properties to CAD Family. However, it is not a best practice. 

The best practice is only to map configuration properties for part and assembly content types.

7) Create Custom Attributes

Platform Management > Content > Collaborative Spaces Configuration Center > Attributes Management

a) Create File Properties as Custom Attributes

When you use attribute mapping, it is a best practice to make SOLDWORKS Design the single-source-of-truth for your additional information. In other words, your file properties drive the additional information that you see in 3DEXPERIENCE. To start, you typically create a copy of your file properties as custom attributes. 

NOTE: If you are new to this topic, only create one custom attribute so you can test the functionality and learn how it works. Add more custom attributes after you are comfortable with the tools and understand all the steps.

The numbers in the following figures depict the steps that you must follow to create custom attributes for a content type.

The only requirement is the Name (7). After you create a custom attribute, it is impossible to change the Name. If you require a different name, you must delete the custom attribute. For this parameter, you can only use alphanumeric characters, and you cannot use spaces. There are also several forbidden character strings. Notifications such as the following appear when you encounter a limitation:

Repeat steps 5-8 for all content type mappings you want to map, then click Apply (9). 
 

IMPORTANT: Do not create the following names as custom attributes:

Revision
Revision Comment
Description
Title

These attributes are default attributes, and they are automatically available for mapping.

i) Optional Parameters

Some optional parameters have important distinctions to know about and consider.
 

1. Title

The Title parameter is optional. However, it is a best practice to use. It is a user-friendly name for your custom attributes. The title can include spaces, it has fewer restrictions than Name, and you can change the title value after creation.
 

2. Default Value

You can only specify Default Value parameters when no other custom attributes exist for a content type.

For example, during an initial tenant setup you create custom attributes. Then you migrate SOLIDWORKS Design files to your collaborative spaces. Time passes and you realize that you want to add a custom attribute that has a default value. Or, you want to edit an existing custom attribute and add a default value for it. In this scenario, you cannot specify a default value for new or existing custom attributes. To reactivate this parameter, you must delete all attribute mappings, delete all custom attributes for the content type, and reload the server cache. 
 

3. Mandatory

The Mandatory parameter works together with the Mandatory mapped Attributes setting in:

Platform Management > Content > Collaborative Spaces Configuration Center > CAD Collaboration > SOLIDWORKS > Settings > Save

The platform only enforces the rule when you create content from SOLIDWORKS Design. It does not enforce the rule when you create content using the Create new on 3DEXPERIENCE platform feature in SOLIDWORKS Design. It also does not enforce the rule when you create SOLIDWORKS Design content from a 3DEXPERIENCE web app, like Product Structure Editor.

4. Read-Only

The Read-Only parameter means that you can only specify the value from SOLIDWORKS Design. Therefore, you must map it from SOLIDWORKS Design to 3DEXPERIENCE. Optionally, to indicate in 3DEXPERIENCE that the custom attribute is read-only, you can create a mask file. See section 9 for more information.
 

5. Other Parameters

Details about the other optional parameters are outside the scope of this document.

b) Reload Server Cache

Platform Management > Content > Collaborative Spaces Configuration Center > Configuration Deployment > Configuration and Server Utilities

After applying your custom attributes, the following notification appears:

You must reload the server cache to finalize the deployment of your custom attributes.
 

i) Update Index Model 

If you activate the Searchable parameter in any custom attributes, then you must also update the index model. Updating the index model allows those custom attributes to display in search results.

When you click Update Index Model, the following notification appears:

If you update again, you see this notification:

The numbers in the following figures depict the steps to complete these tasks.

You must reload the server cache so that collaborative spaces see the new attributes. When you click Reload Cache, you see one the following notifications:

The second notification can indicate that the 3DSpace infrastructure that services your tenant are busy or actively processing other information. There is no need to reload again.

Completion of these tasks depends on the amount of content in your collaborative spaces and the number of attributes that you create. Do not expect to see completion notifications. Consider these tasks complete when you see the new attributes in your content and see the new attributes in search results, if applicable.
 

c) Attributes Propagation

If you create or edit custom attributes after content creation, then it is a best practice to go through the attributes propagation process. This process ensures that the changes apply to the existing content. 

If your tenant has multiple administrators, then go through this process periodically to ensure that content is always up to date. 

Platform Management > Content > Collaborative Spaces Configuration Center > Configuration Deployment > Attributes Propagation

Click Search. If green check marks appear next to content types, then there are no changes to propagate.
 

If orange check marks appear next to content types, then that data does not have the new or updated custom attributes. Select those content types, click Propagate, and accept the warning to propagate the attribute changes. 

IMPORTANT: If you propagate attributes, then existing attribute values can be overwritten with default values, if that is the definition of a custom attribute. Often, the value becomes blank.

In this scenario, know that there is no way to propagate file property values to custom attributes. You must resave your SOLIDWORKS Design files to 3DEXPERIENCE to propagate the values.

8) Configure Attribute Mapping

Platform Management > Content > Collaborative Spaces Configuration Center > CAD Collaboration > Connectors > SOLIDWORKS > Attribute Mapping

a) Default Attribute Mappings

By default, the default attributes Description and Title are automatically mapped for Physical Product and Drawing content types. You cannot change the mapping direction for these attributes.

As mentioned in section 7, the default attribute Revision is automatically available for mapping. You cannot choose the mapping direction for this attribute. It only maps from 3DEXPERIENCE to SOLIDWORKS Design.

i) Title Mapping

Mapping of the title attribute is a misunderstood and important topic. In the context of SOLIDWORKS Design and 3DEXPERIENCE, there are two distinct title identifiers: File Title (also called SW Title) and Title (also called Physical Product Title). See Knowledge Base article QA00000070613 for more information on all naming conventions inside SOLIDWORKS Design.

By default, the Title attribute maps unidirectionally from SOLIDWORKS Design to 3DEXPERIENCE. This mapping means that the File Title value propagates to the Title value every time you save a file to 3DEXPERIENCE. With this mapping, there are two ways to edit the File Title so that the Title attribute updates as you expect:

1. Right-click the File Title in the FeatureManager Design Tree and select Rename File Title.
2. Create a configuration property named Title and enter a value.

For Physical Product content that you create by saving parts and assemblies, the Title value you see depends on the structure of the files. There are four structures to consider:

1. Single configuration part or assembly that is not updated for 3DEXPERIENCE compatibility.
2. Single configuration part or assembly that is updated for 3DEXPERIENCE compatibility.
3. Multiple configuration part or assembly that is not updated for 3DEXPERIENCE compatibility.
4. Multiple configuration part or assembly that is updated for 3DEXPERIENCE compatibility.

With single configuration files, the File Title is the same as the Title. When you change either value (even in the scenario where you map the title attribute bidirectionally), the value propagates. 

With single configuration files that you update for 3DEXPERIENCE compatibility, you can also activate the following document property to control the naming.

With multiple configuration files, the File Title is not the Title. The value that propagates to Title is a concatenation of File Title and Configuration Name. The naming convention is File Title(Configuration Name). You cannot change this naming convention, and the parentheses must remain. You must manage the two names separately. 

For example, you have a part with File Title = Part1. The part has two configurations: Default and Config2. When you save this part to 3DEXPERIENCE, the platform creates two Physical Products: Part1(Default) and Part1(Config2). To change the Part1 name, you use one of the two methods described earlier. To change the Default or Config2 name, you edit the configuration properties (for the not updated file structure scenario). Or, you use the Rename Physical Product Configuration command (for the updated file structure scenario).

1) Enterprise Item Number (EIN)

Platform Management > Content > Collaborative Spaces Configuration Center > Engineering Definition > Enterprise Item Number: Admin Configuration

The platform has a setting named Copy Enterprise Item Number to Title of a Product. If you enable this setting, apply an EIN to content you create in SOLIDWORKS Design, and save to 3DEXPERIENCE, the EIN value propagates to the Title. 

This setting does not prevent you from editing the Title. If you change the File Title and save to 3DEXPERIENCE, the File Title value propagates to the Title value.

If you require for the Title to be the EIN, then create two configuration properties:

• Enterprise Item Number = \\\$PLMPRP:"EnterpriseExtension.V_PartNumber"
• Title = \\\$PRP:"Enterprise Item Number"

These configuration properties ensure that SOLIDWORKS Design reads the EIN from 3DEXPERIENCE and propagates it to the Title attribute with every save.

Alternatively, you can activate the document property from Figure 37 to prevent the title from changing.

b) Custom Attribute Mappings

The numbers in the following figures depict the steps that you must follow to configure attribute mapping.

NOTE: The ability to map custom properties for part and assembly content types became unavailable in R2026x FD01 (February 2026). If your 3DEXPERIENCE subscription started before that date, then you can map custom properties to CAD Family. However, it is not a best practice. 

The best practice is only to map configuration properties for part and assembly content types.

Repeat steps 3-7 for all content types and file properties that you want to configure. 

The best practice is to use unidirectional mapping, from SOLIDWORKS Design to 3DEXPERIENCE, for all custom attributes. For example, Component (Family Item) to Physical Product. Unidirectional mapping optimizes performance and ensures that SOLIDWORKS Design is the single-source-of-truth for this additional information.

When you use bidirectional mapping or unidirectional mapping, from 3DEXPERIENCE to SOLIDWORKS Design, those custom attributes become available in the PLM Attributes list.
 

When complete, click Apply. You do not need to reload server cache or update the index model after applying the mappings. 
 

IMPORTANT: You can delete, reset, and re-create any attribute mapping, at any time, without affecting the custom attributes themselves. This methodology is useful to identify if a specific attribute mapping is the cause of a problem. 

For example, an incorrect attribute mapping can cause an error when you save SOLIDWORKS Design files to 3DEXPERIENCE. Or, too many attribute mappings can degrade open and save performance. Your tenant administrator can click Reset to clear all attribute mappings. Then you can retest your scenario to see if the problem is fixed. If it is, then add the attribute mappings back one at a time to identify the problem or bottleneck.

i) Weldments

If you map cut list properties, then the data type for the custom attribute must be a String. It is a best practice to specify these types of custom attributes as Read-Only so that the values can only come from SOLIDWORKS Design. Therefore, the mapping must be from SOLIDWORKS Design to 3DEXPERIENCE. 

NOTE: Custom attribute names are case-sensitive. When you map cut list properties, the names become important since SOLIDWORKS Design tends to use all caps naming conventions for cut list properties.

9) Attribute Mapping in Use

After you create custom attributes, configure mapping, and validate the behavior, invite users to your tenant and start to create content.

a) View and Edit Custom Attributes

In SOLIDWORKS Design, there are three ways to view and edit custom attributes:

• File Properties dialog box
  • File > Properties

NOTE: You can also use the Custom Properties task pane, with custom property templates. It is an extension of the File Properties dialog box.

• PLM Properties dialog box
  • CommandManager > Lifecycle and Collaboration > PLM Properties
  • MySession > Action Bar > View > PLM Properties
  • Right-click an object in MySession > Properties
• 3DEXPERIENCE Properties tab
  • MySession > Action Bar > View > Side Panel > Properties

i) File Properties

The File Properties dialog box is the most familiar and informative. It is the source of truth and displays the values that propagate to 3DEXPERIENCE when you save. In this dialog box, you have full editing rights to all file properties, visibility to PLM attributes, and visibility to expressions like \\\$PRP and \\\$PLMPRP.
 

ii) PLM Properties

The PLM Properties dialog box displays all attributes for an object, and it opens in edit mode. If the object has multiple configurations, you can click Switch to Family to view the properties of the parent CAD Family object. You have limited editing rights to mapped attributes when the object is not in a released maturity state. The ability to edit mapped attributes in this dialog box can be misleading. 

For example, in Figure 46, the Mass file property (which has a \\\$PRP expression) is mapped from SOLIDWORKS Design to 3DEXPERIENCE. SOLIDWORKS Design calculates the value of this file property, and you can only change the value in SOLIDWORKS Design. However, the value of this file property shows as editable in the PLM Properties dialog box. If you edit the value, it does not propagate to SOLIDWORKS Design. The value "resets" the next time you open or reload the object from the server.  

In this dialog box, you can also edit some PLM attributes, like Revision Comment. However, the edits do not propagate to SOLIDWORKS Design and the File Properties dialog box until you reload the data from the server. 
 

iii) 3DEXPERIENCE Properties

The 3DEXPERIENCE Properties tab has most of the same functionality as the PLM Properties dialog box. It displays all attributes for an object, and it opens in read-only mode. You must click Edit to change values. 
 

1) Mask Files for Properties

Your platform administrator can customize how the attributes display for a given content type by creating a Mask File. When you apply a mask file, your customized layout applies to all properties viewing dialog boxes and apps in 3DEXPERIENCE. See the Mask File Syntax for Properties page if the User Assistance for more information.
 

b) Attribute Checks

When you save SOLIDWORKS Design files to 3DEXPERINCE, the following attribute checks occur:

• Custom attributes with a Boolean data type must map to file properties with a Yes or no data type. If the data type does not match, then the platform ignores the file property on save and it does not propagate to 3DEXPERIENCE.
• Custom attributes with a Date data type must map to file properties with a Date data type.
• Custom attributes with a Real and Integer data type must map to file properties with a Number data type.
• If custom attributes have a range of Authorized Values, then the platform checks the file properties values for a match.
• If the value of custom attributes with a String data type exceeds 256 characters, then the platform truncates the value and adds an ellipsis to the end of the value.

If any of these checks fail, a Wrong attribute value warning displays in the Save to 3DEXPERIENCE dialog box.
 

i) Incompatible Property Value Example

The following example shows how the incompatible property value check works. 

In 3DEXPERIENCE, there is a a custom attribute for physical products named Print3D. It has a Boolean data type and mapping from SOLIDWORKS Design to 3DEXPERIENCE with a file property named 3D Print.

In a SOLIDWORKS Design part file, a configuration property named 3D Print exists. It has a Text data type.

You save the part to 3DEXPERIENCE. The Save to 3DEXPERIENCE dialog box displays an Incompatible property value warning for the status.

You click the warning to display more information.

In this example, the dialog box tells you exactly what the problem is. The data type for the 3D Print file property must be Yes or no.

Although the system does not block the save, if you want the property value to propagate, then you must change the data type to Yes or no. If you do not, the value shows as blank in 3DEXPERIENCE.

10) Limitations, Tips and Troubleshooting

• It is a best practice for the platform administrator to verify the deployment of attributes after every 3DEXPERIENCE platform SaaS update or upgrade.
• You cannot edit or delete a custom attribute if a) the platform is actively mapping it or b) a maturity graph control rule is referencing it. If you attempt to delete a custom attribute in this state, the following notification displays. You must delete the attribute mapping, then you can edit or delete the attribute.

• If you create a duplicate revision customer attribute, then you cannot define an Enterprise Item Number (EIN) formula, and the Engineering Definition page of Collaborative Spaces Configuration Center does not load.
• Only map from 3DEXPERIENCE to SOLIDWORKS Design with default attributes or with custom attributes you only plan to reference or read from.
• If a file property has mapping from 3DEXPERIENCE to SOLIDWORKS Design, and the Value/Text Expression of it has an expression like: SW-Material@@Default@@Part1.SLDPRT, \\\$PRP:"SW-File Name", or a dimension expression, then the platform ignores the mapping. In this scenario, the attribute mapping functions as SOLIDWORKS Design to 3DEXPERIENCE to prevent 3DEXPERIENCE from unintentionally deleting property expressions.
• If you create content with file properties, then create custom attributes and mapping to those file properties, the default value of the custom attribute overwrites the property value during open or reload from the server. To prevent this, lock and save to 3DEXPERIENCE. Saving synchronizes the file properties with the new custom attributes.
• There is no way for a platform administrator to reindex all the data in their tenant. If content already exists and you create custom attributes, the custom attributes propagate to the existing content. However, you cannot find the existing content by searching for custom attributes. This is because the index is not up to date. All of you data is reindexed after a Functional Delivery (FD) or major (GA) update. The same is true if you delete custom attributes. This limitation is the meaning behind the following warning:

• Avoid mapping many custom attributes. Doing so can severely impact the open and save time for files that have many configurations. For example, it about 15 minutes for the MySession app to refresh PLM information when you open a part that has 900 configurations and 45 mapped custom attributes. With only 2 mapped custom attributes, the same PLM information refreshed in about 20 seconds.
   

11) Frequently Asked Questions

• My administrator made changes to some custom attributes or settings. Why does the mapping of file properties not work correctly?

Any time server-side changes are made, you must restart SOLIDWORKS Design.
 

• Why do I not see the PLM Attributes in the Property Name list?

PLM attributes depend on a custom properties architecture that was introduced in SOLIDWORKS 2018. If your files were created using a document template from SOLIDWORKS 2017, or older, then you must upgrade the custom properties.

Open your files and right-click the file title in the FeatureManager Design Tree. If you see the Upgrade custom properties option, then your files use the old custom properties architecture. 

Alternatively, you can update your files for 3DEXPERIENCE compatibility. The Update for 3DEXPERIENCE compatibility option upgrades custom properties as well.

You can use the 3DEXPERIENCE Transition task, in the SOLIDWORKS Task Scheduler, to upgrade custom properties or update for 3DEXPERIENCE compatibility in bulk.

• Why do I not see custom attributes in the Property Name list of the Properties dialog box?

Custom attributes only display in the Property Name list if attribute mapping is bidirectional or from 3DEXPERIENCE to SOLIDWORKS.
 

• How do I map a file property like mass, with units, to 3DEXPERIENCE? 

From the information in Table 4, use the highlighted data type mapping. In SOLIDWORKS Design, define your file property with an Equation data type. In 3DEXPERIENCE, define your custom attribute with a Real + Dimensions (Unit) data type.
 

The only supported dimensions (unit) are length, mass, angle, or any combination of those three dimensions (like area, volume, or density). 

For example, in SOLIDWORKS Design, this weldment part is set to the MKS (meter, second, kilogram) unit system. It has a configuration property named Mass with an Equation data type. The property evaluates to 114.91. Because of the MKS unit system, the value is in kilograms.

In 3DEXPERIENCE, a custom attribute named Mass, with a Real data type exists. The Dimensions (Unit) parameter is set to Mass, and the Display Unit is set to kg.

Create attribute mappings, from SOLIDWORKS Design to 3DEXPERIENCE, for the configuration and the weldment content type.

With this configuration, the value of the file property propagates to 3DEXPERIENCE with the correct value and unit.
 

• In 3DEXPERIENCE, why is the dimensional value of a custom attribute not the same as the value of its mapped file property in SOLIDWORKS Design?

The system only reads file property values as MKS (meter, kilogram, second). This is a limitation of the SOLIDWORKS Design API. It takes that value and converts it to the Dimensions (Unit) that you specify in the custom attribute. 

For example, a weldment part is set to the IPS (inch, pound, second) unit system, and the length of a cut-list item is 259.84 inches. A custom attribute named Length, with a Real data type exists. The Dimensions (Unit) parameter is set to Length, and the Display Unit is set to in. The file property and custom attribute are mapped.

The value of the file property in 3DEXPERIENCE shows as 10229.92 inches. This value is correct. The system reads the file property value as 259.84 meters and converts that value to inches. 259.84 meters * 39.3701 = 10229.92 inches. 

There are two options to display the 259.84 inches value in 3DEXPERIENCE:

a. In SOLIDWORKS Design, set the unit system to MKS or set the Length unit to meters.
b. In 3DEXPERIENCE, create a custom attribute with a Real data type, without a Dimensions (Unit) parameter. Add the unit (inches) to the Name or Title parameters.
 

• What information do I need to provide to support to investigate an attribute mapping problem?

- A SOLIDWORKS Rx package from a computer that can reproduce the scenario, including the relevant document templates and a sample file set.
- An export of your tenant configuration. Your platform administrator can do this from:

Collaborative Spaces Configuration Center > Configuration Deployment > Import and Export Configuration > Export

The resulting XML files contains the definition of all your custom attributes and attribute mappings.

Your Feedback Requested
We would like to hear your feedback and suggestions for new topics. After reviewing this document, please take a few minutes to fill out a brief survey. Your feedback will help us create the content that directly addresses your challenges.