MS_DESIGNSEED

Hello,

I have defined the variable MS_DESIGNSEED correctly.

MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed\aaprog-seed-2D.dgn

But when I am making a new file the seed file suggested is not the one pointed to by the variable MS_DESIGNSEED but the last one that was used.

Is this WAD? I would prefer I could force people to use a particular seed file (or at least I would like that the seed file that is suggested is always the correct one).

Furthermore: when i click on browse (right from the suggested seed file) I am not directed to the directory MS_DESIGNSEED is pointing to. As far as I could figure out this has to do something with the space in the path: C:\ProgramData\Bentley\CONNECT Edition\Configuration\Organization\Seed

Thanks for any input!

Luc Dierick

Parents
  • Luc Dierick said:

    I have defined the variable MS_DESIGNSEED correctly.

    MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed\aaprog-seed-2D.dgn

    Are you sure?

    • It's preferable to use a forward slash as a folder separator in your configuration file:
    MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed/aaprog-seed-2D.dgn
    • If _USTN_ORGANIZATION is incorrectly defined, then your definition that relies on _USTN_ORGANIZATION will also be ill-defined.

    Our freeware Configuration Variable Validator will tell you if a configuration variable is correctly defined.

     
    Regards, Jon Summers
    LA Solutions

Reply
  • Luc Dierick said:

    I have defined the variable MS_DESIGNSEED correctly.

    MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed\aaprog-seed-2D.dgn

    Are you sure?

    • It's preferable to use a forward slash as a folder separator in your configuration file:
    MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed/aaprog-seed-2D.dgn
    • If _USTN_ORGANIZATION is incorrectly defined, then your definition that relies on _USTN_ORGANIZATION will also be ill-defined.

    Our freeware Configuration Variable Validator will tell you if a configuration variable is correctly defined.

     
    Regards, Jon Summers
    LA Solutions

Children
  • I had the same exact issue when I was setting up our standards.cfg file. What I discovered was that I had manually navigated to a file to use as a seed when I started setting things up and that was taking ownership (don't ask me why) of this variable.

    I had new users who had never touched that field when making a new file attempt to make a new file and it pointed at the correct seed file working as I expected. I then manually navigated myself to the correct seed and it worked fine. We only use one seed file and I haven't set up any work space/sets yet so I have no idea what will happen long term the issue might come back.