PW integration with OpenBuildings Designer

Hi,

I installed the latest edition of OBD Update 5 but cannot make it working with PW Explorer 10.00.03.49. I know it's not the most up to date version of PW but my IT department is reluctant to update it. Is it possible to make these two working together?

I've also got the latest Microstation Connect Edition Update 13 and it works fine with PW.

Parents
  • Hi Ranit,

    The content of the BuildingDesigner_PW.cfg is below.

    Regarding the issue, when I start either Microstation or Aecosim they both connect to PW datasource and PW explorer windows pops up. I also have an ability to update server copy and refresh local copy from FILE menu. With OBD I don't have any of these.

    When copying the content of BuildingDesigner_PW.cfg I noticed this entry:

    [ProjectWiseIntegration]
    PW_DISABLE_INTEGRATION_FROM_DESKTOP:1

    Should I change it to 0 to enable integration? 

    #--------------------------------------------------------
    # OpenBuildings | ProjectWise Configuration Variables
    #--------------------------------------------------------
    
    
    [ProjectWiseIntegration]
    PW_DISABLE_INTEGRATION_FROM_DESKTOP:1
    
    %if defined (_PWEXPLORER)
    _PWCUSTOMINTEGRATION=1
    TFPW_LOADED=PWEXPLORER
    %else
    %if !defined (PW_DISABLE_INTEGRATION_FROM_DESKTOP)
    TFPW_LOADED=PWDESKTOPINTEGRATION
    %endif
    %endif
    #
    
    %if defined (_PWEXPLORER) || !defined (PW_DISABLE_INTEGRATION_FROM_DESKTOP)
    MS_CFGVARS_APPS > tfpw
    #
    # If set to '1',provides ProjectWise integration and access to the ProjectWise repository for the
    # following building features; Column Grid tool , Frame Builder, Structural Section, Compound Cell Manager and Quantify Tool.
    #TFPW_REFDATA_USE_PW_DLG = 1
    #
    # If set to '1', uses ProjectWise extension associations when creating new files to determine the application assignment.
    # If set to '0', or not defined then the application associated to the newly created file will be inherited from the parent file
    #TFPW_USE_EXT_ASSOCIATIONS = 1
    #
    # If set to '1', then
    # If set to '0', or not defined then
    #TFPW_D_CHECKSOUTBXSALSO = 1
    #
    # If set to '0' or not defined, then ProjectWise check-in dialog is suppressed, when editing DataGroup data across references, references are automatically checked back into ProjectWise
    # If set to '1', then the ProjectWise check in dialog is presented when editing DataGroup data across references
    BBPW_DG_EDIT_PROMPT_CHECKIN = 0
    %endif
    #
    

  • Hi Rafal,

    Put a "#" in front of the configuration variable named "PW_DISABLE_INTEGRATION_FROM_DESKTOP : 1" to comment it out. Then save the file and run OBD. From then onwards, every time the application runs, desktop integration should be triggered.

    Regards,

    Ranit

    Answer Verified By: Rafal Razmus 

  • I commented out both rows 6 and 7. It didn't work initially but I remembered there is a configuration variable called PW_DISABLEDESKTOPINTEGRATION or something similar. It was set to '0' so logically the integration should work. For some weird reason it didn't. Only after I deleted this variable the integration started working. Don't see any sense in this but I am glad the problem is sorted :).

    Thank you.

    Answer Verified By: Rafal Razmus 

Reply
  • I commented out both rows 6 and 7. It didn't work initially but I remembered there is a configuration variable called PW_DISABLEDESKTOPINTEGRATION or something similar. It was set to '0' so logically the integration should work. For some weird reason it didn't. Only after I deleted this variable the integration started working. Don't see any sense in this but I am glad the problem is sorted :).

    Thank you.

    Answer Verified By: Rafal Razmus 

Children
No Data