Design Assistant didn't work with project export for DGN-SSS2 TIER Persistence

Hello,
I use the Electric Data Modeling Administrator to export my own project and load a Expect Designer database.

When I export a project for DGN-SSS2TIER persistence model and open the Expect Designer and try to place new feature in the Design Assistant, it doesn't create work point or path.

I tried to export a project for DGN persistence model and the Design Assistant worked fine.

My question is how to export a project and load database for DGN-SSS2TIER persistence mode?

Parents
  • Hi Nikolay,
    Did you export the workspace and load the database? That is, did you run both the export_BentleyUD_SSS2T_ and the LoadIntoDB macros?
    The export macro creates the workspace, but the LoadIntoDB populates the database. If they are out of synch you would get the result you are describing.
    Thanks,
    Mike


    This is a test

  • Hi Mike,

    I do exactly same steps :

    1. Export the workspace

    2. Export SQL Script for Utility schema and Execute in WP Database (BUDV8i)

    3. Load Database

    Result is: I please features but Design Assistant didn't create a pat.

    P.S.

    I check log file from export_BentleyUD_SSS2T and I find Warning - Unknown or Empty XML Fragment File: C:\Program Files (x86)\Bentley\UtilitiesDesigner V8i\UtilitiesDesigner\DataModel\Common\xmlFragments\BUC-SQLServer2-Tier-BUIS.xml" my installation is default and this file is not exist.

    Can you tell me where can I find this file?

    Thanks,

    Nikolay

Reply
  • Hi Mike,

    I do exactly same steps :

    1. Export the workspace

    2. Export SQL Script for Utility schema and Execute in WP Database (BUDV8i)

    3. Load Database

    Result is: I please features but Design Assistant didn't create a pat.

    P.S.

    I check log file from export_BentleyUD_SSS2T and I find Warning - Unknown or Empty XML Fragment File: C:\Program Files (x86)\Bentley\UtilitiesDesigner V8i\UtilitiesDesigner\DataModel\Common\xmlFragments\BUC-SQLServer2-Tier-BUIS.xml" my installation is default and this file is not exist.

    Can you tell me where can I find this file?

    Thanks,

    Nikolay

Children
  • Hi Nikolay,

    I suspect that the feature names in the database are not being prepended with the SQL Server schema name, but I am not sure why.

    Can you run this script on your database? (You don't need to run the export or LoadIntoDB macros again)

    USE [BUDV8i]

    GO

    /**** Update featuretype gistable ****/

    update CHDATA.FEATURETYPE SET GISTABLE = REPLACE(GISTABLE, GISTABLE, DATASET + '_' + GISTABLE)

    GO

    /**** Update compoundfeature childtablename ****/

    UPDATE A

    SET A.CHILDTABLENAME = REPLACE(A.CHILDTABLENAME, A.CHILDTABLENAME, B.DATASET + '_' + A.CHILDTABLENAME)

    FROM CHDATA.COMPOUNDFEATURE A, CHDATA.FEATURETYPE B

    WHERE A.CHILDID = B.ID

    GO

    /**** Update commoditygroup workspace ****/

    update CHDATA.COMMODITYGROUP SET WORKSPACE = REPLACE(WORKSPACE, '_DGN', '_SSS')

    GO

    /**** Update commoditygroup Masterpath ****/

    update CHDATA.COMMODITYGROUP SET MASTERPATH = REPLACE(MASTERPATH, '_DGN', '_SSS')

    GO

    If this does not correct it, then please run the following script to reverse that change:

    USE [BUDV8i]

    GO

    /**** Update featuretype gistable ****/

    update CHDATA.FEATURETYPE SET GISTABLE = REPLACE(GISTABLE, DATASET + '_', '')

    GO

    /**** Update compoundfeature childtablename ****/

    UPDATE A

    SET A.CHILDTABLENAME = REPLACE(A.CHILDTABLENAME, B.DATASET + '_', '')

    FROM CHDATA.COMPOUNDFEATURE A, CHDATA.FEATURETYPE B

    WHERE A.CHILDID = B.ID

    GO

     

    /**** Update commoditygroup workspace ****/

    update CHDATA.COMMODITYGROUP SET WORKSPACE = REPLACE(WORKSPACE, '_SSS', '_DGN')

    GO

    /**** Update commoditygroup Masterpath ****/

    update CHDATA.COMMODITYGROUP SET MASTERPATH = REPLACE(MASTERPATH, '_SSS', '_DGN')

    GO

    Hope that helps,

    Mike


    This is a test

    Answer Verified By: Nikolay Tsonev 

  • Thanks Mike,


    You are right the feature names is different in Workspace and Database.


    I added one more checkbox in frmLoadIntoDb Form to set MA to load right data in database.


    For others  have same problem I attached VBA Form.

    frmLoadIntoDb.zip

    Answer Verified By: Nikolay Tsonev