AnsweredAssumed Answered

Mapping Model Custom Properties to Drawing's Data Card Not Working

Question asked by Sally Hoo on Aug 29, 2012
Latest reply on Aug 30, 2012 by Sally Hoo

Like • Show 0 Likes0
Comment • 10

I'm trying to map the referenced model's custom properties of a SLDDRW file to the drawing's data card in PDM. I have followed the instructions at http://help.solidworks.com/2012/English/EnterprisePDM/Admin/t_SolidWorks_PRPSHEET_links.htm and have not been able to get the properties to map. I've made sure to enable the EPDM add-in in SolidWorks and as directed in the admin guide have opened the drawing, made a change, saved the drawing, and checked it back in. I'm still not getting anything to show up in the data card. I've attached an example of one of the variable mappings.

Does anyone have any idea where I'm going wrong?

Sally Hoo Aug 30, 2012 3:23 PM

Correct Answer

I think I figured it out. After importing and checking in the part and associated drawing into the vault, the drawing's reference was still to the part on my local C: drive (the PDM check-in window said that the referenced part was to the version in the vault, but when actually finding references within SolidWorks, it was still going to the part on my local C: drive... I had to break the link by renaming the folder on my C: drive and then checking back in). After doing so, it grabbed the properties the way it was supposed to.

Which leads me to my second point - it's really going to be a serious pain to have to open all the drawings I import in order to get the part references corrected. Is there any way to get around this?

See the reply in context

No one else had this question

Outcomes

Jeff Sweeney Aug 29, 2012 9:29 PM

Do you have "slddrw" in your CustomProperty line? It needs to be in both.

Actions

Sally Hoo @ Jeff Sweeney on Aug 29, 2012 9:47 PM

I tried it both ways. With slddrw listed in the CustomProperty block, I'm getting the drawing's custom properties pulled into the data card. With slddrw not listed in the CustomProperty block, I'm not getting anything in the data card.

Actions

Tim Read @ Sally Hoo on Aug 30, 2012 3:06 AM

Hi Sally,

What version of Solidworks / EPDM are you running? Older versions (2010 and earlier) require the SQLDMO drivers installed for the "Sharing" in SolidWorks to work and on x64 they sometimes did not - bug.

See S-014092 in the knowledge base

Actions

Sally Hoo @ Tim Read on Aug 30, 2012 11:08 AM

Hi Tim,

I'm on EPDM 12.3 and SolidWorks 2010. Since I don't have access to the knowledge base, I was wondering if you knew any more details about the SWLDMO drivers. Specifically, where does it need to be installed? On the archive servers or on all of the users' computers or both?

Actions

Tim Read @ Sally Hoo on Aug 30, 2012 11:24 AM

Hi Sally,

It needs to be installed on both the Archive Servers and all of the clients... it is part of the 2005 Backwards Compatibility

You can find it on the install media

From the Knowledge base:

If the SQL-DMO drivers have not been correctly installed on the client, some operations in the file vault will fail. A common error that shows is 'The Archive Server does not have SQLDMO installed.' when trying to log in to the file vault from the Administration tool.

The SQL-DMO drivers for SQL 2005 connectivity are normally installed as a prerequisite during PDMWorks Enterprise installation procedure.

Solution:

Re-install SQL-DMO by running the “SQLDMO 2005 backwards compatibility install” from the setup CD (note that it will install correct SQLDMO drivers even if using SQL2000 or 2008 server). The install is found under \Setup\ISSetupPrerequisites\{2A2B0450-D83A-4779-B083-FC7E50A1BB86}\SQLServer2005_BC.msi or can be downloaded from www.microsoft.com.

Note that if installing on a 64-bit OS you should run the install from the \Setup64\ISSetupPrerequisites\... folder instead.

If the backwards compatibiliy installer detects that the drivers are already installed, you are recommended to proceed with uninstalling them and then re-run the installation again to ensure they become correctly registered.

OR...

Download from Microsoft:

On 32bit install SQLServer2005_BC.msi

On 64bit install SQLServer2005_BC_x64.msi

Actions

Michael Dekoning @ Sally Hoo on Aug 30, 2012 11:28 AM

Sally,

SQL-DMO is not required for Enterprise PDM 2012.

Actions

Michael Dekoning @ Sally Hoo on Aug 30, 2012 9:39 AM

Jeff is correct. Both CustomProperty and $PRPSHEET need to have the slddrw extension.

Long shot here but is the attribute entered exactly the same as the property including the case? It has to match exactly. In other words, based on your mapping the property can't be uppercase like PARTNO. We've been bitten by this a few times.

Actions

Sally Hoo Aug 30, 2012 3:23 PM

Actions

Jeff Sweeney @ Sally Hoo on Aug 30, 2012 4:55 PM

Try highlighting the file and using the "Update References" tool from the tools menu.

Actions

Sally Hoo @ Jeff Sweeney on Aug 30, 2012 5:02 PM

No luck. The update references tool already shows the vault version reference, so updating just "updated" to the same file. In SolidWorks, it still shows up as a reference to my local hard drive.

Actions

10 Replies

Jeff Sweeney Aug 29, 2012 9:29 PM
Mark Correct
Correct Answer
Do you have "slddrw" in your CustomProperty line? It needs to be in both.
Like • Show 0 Likes0
Actions
- Sally Hoo @ Jeff Sweeney on Aug 29, 2012 9:47 PM
  Mark Correct
  Correct Answer
  I tried it both ways. With slddrw listed in the CustomProperty block, I'm getting the drawing's custom properties pulled into the data card. With slddrw not listed in the CustomProperty block, I'm not getting anything in the data card.
  Like • Show 0 Likes0
  Actions
  - Tim Read @ Sally Hoo on Aug 30, 2012 3:06 AM
    Mark Correct
    Correct Answer
    Hi Sally,
    
    What version of Solidworks / EPDM are you running? Older versions (2010 and earlier) require the SQLDMO drivers installed for the "Sharing" in SolidWorks to work and on x64 they sometimes did not - bug.
    
    See S-014092 in the knowledge base
    Like • Show 0 Likes0
    Actions
    - Sally Hoo @ Tim Read on Aug 30, 2012 11:08 AM
      Mark Correct
      Correct Answer
      Hi Tim,
      
      I'm on EPDM 12.3 and SolidWorks 2010. Since I don't have access to the knowledge base, I was wondering if you knew any more details about the SWLDMO drivers. Specifically, where does it need to be installed? On the archive servers or on all of the users' computers or both?
      Like • Show 0 Likes0
      Actions
      - Tim Read @ Sally Hoo on Aug 30, 2012 11:24 AM
        Mark Correct
        Correct Answer
        Hi Sally,
        
        It needs to be installed on both the Archive Servers and all of the clients... it is part of the 2005 Backwards Compatibility
        
        You can find it on the install media
        
        From the Knowledge base:
        If the SQL-DMO drivers have not been correctly installed on the client, some operations in the file vault will fail. A common error that shows is 'The Archive Server does not have SQLDMO installed.' when trying to log in to the file vault from the Administration tool.
        
        The SQL-DMO drivers for SQL 2005 connectivity are normally installed as a prerequisite during PDMWorks Enterprise installation procedure.
        
        Solution:
        
        Re-install SQL-DMO by running the “SQLDMO 2005 backwards compatibility install” from the setup CD (note that it will install correct SQLDMO drivers even if using SQL2000 or 2008 server). The install is found under \Setup\ISSetupPrerequisites\{2A2B0450-D83A-4779-B083-FC7E50A1BB86}\SQLServer2005_BC.msi or can be downloaded from www.microsoft.com.
        
        Note that if installing on a 64-bit OS you should run the install from the \Setup64\ISSetupPrerequisites\... folder instead.
        
        If the backwards compatibiliy installer detects that the drivers are already installed, you are recommended to proceed with uninstalling them and then re-run the installation again to ensure they become correctly registered.
        
        OR...
        
        Download from Microsoft:
        
        On 32bit install SQLServer2005_BC.msi
        On 64bit install SQLServer2005_BC_x64.msi
        Like • Show 0 Likes0
        Actions
      - Michael Dekoning @ Sally Hoo on Aug 30, 2012 11:28 AM
        Mark Correct
        Correct Answer
        Sally,
        
        SQL-DMO is not required for Enterprise PDM 2012.
        Like • Show 0 Likes0
        Actions
  - Michael Dekoning @ Sally Hoo on Aug 30, 2012 9:39 AM
    Mark Correct
    Correct Answer
    Jeff is correct. Both CustomProperty and $PRPSHEET need to have the slddrw extension.
    
    Long shot here but is the attribute entered exactly the same as the property including the case? It has to match exactly. In other words, based on your mapping the property can't be uppercase like PARTNO. We've been bitten by this a few times.
    Like • Show 0 Likes0
    Actions
Sally Hoo Aug 30, 2012 3:23 PM
Unmark Correct
Correct Answer
I think I figured it out. After importing and checking in the part and associated drawing into the vault, the drawing's reference was still to the part on my local C: drive (the PDM check-in window said that the referenced part was to the version in the vault, but when actually finding references within SolidWorks, it was still going to the part on my local C: drive... I had to break the link by renaming the folder on my C: drive and then checking back in). After doing so, it grabbed the properties the way it was supposed to.

Which leads me to my second point - it's really going to be a serious pain to have to open all the drawings I import in order to get the part references corrected. Is there any way to get around this?
Like • Show 0 Likes0
Actions
- Jeff Sweeney @ Sally Hoo on Aug 30, 2012 4:55 PM
  Mark Correct
  Correct Answer
  Try highlighting the file and using the "Update References" tool from the tools menu.
  Like • Show 0 Likes0
  Actions
  - Sally Hoo @ Jeff Sweeney on Aug 30, 2012 5:02 PM
    Mark Correct
    Correct Answer
    No luck. The update references tool already shows the vault version reference, so updating just "updated" to the same file. In SolidWorks, it still shows up as a reference to my local hard drive.
    Like • Show 0 Likes0
    Actions

Mapping Model Custom Properties to Drawing's Data Card Not Working

Outcomes

Related Content

Recommended Content