Projectwise directory missing from Geopak Project Manager

make sure that this variable is not set GPK_PROJMGR_PROJECTDIR, or you can set it if you have all your projects in the same location, maybe specifying a parent folder for all

If we don't set the variable, project manager will default to the last used project directory, in which case, it's impossible to navigate to the correct directory since the directory is mysteriously missing from the list.  

If we set it to the correct project, it works for most people, however some users automatically default to the last used project directory requiring us to delete the geopak RSC's.  Unfortunately, not everyone in the company has access to their user app data to delete the geopak RSC's.

We also noticed when we set our project directory (since we're doing a hybrid pw managed workspace with *.PCF override/supplementals, how we define the GPK_PROJMGR_PROJECTDIR needs to be start with pw:\ instead of pw://<domain>

Is there a reason or a fix as to why some folders are missing in Project Manager?

each project should have a .prj file and a prjdbs folder. if the prj files and prjdbs folders have been moved from their original locations, they will not work well, you can create new projects and move the runs from the old projects.

the PRJ and the PRJDBS are in the correct locations and haven't been moved.

We have 1200 directories that GEOPAK pulls from, so I thought it might have a max amount, however I ran a test on my local with similar character counts with over 1400 directories, and all directories on the local are accounted for.

This fixed the issue, although we'll need to make sure every user has their permissions or redirect the rsc's to working directories. Is there any idea why the projects would be missing from the GEOPAK List?

Thanks Nico!

I am not sure.
you can also set the force variable which will ignore the resource file and always use the project manager directory specified in the variable
GPK_PROJMGR_PROJECTDIR < pw:\\Alpo.bentley.com:alpo-alpo\Documents\Civil\GEOPAK\Beebe\Road 1\
GPK_FORCE_PROJMGR_PROJECTDIR = 1

We noticed when selecting folders manually, Geopak truncates the PW directory . We want to create generic variable definitions for paths in our workspace like defining "_USTN_PROJECTDATA = $(dms_project(_DGNDIR))4-0-Production/4-01-Drawings/" and then using $(_USTN_PROJECTDATA) for our Geopak variables.

$(dms_project(_DGNDIR) creates the pw://[datasource]Documents/projects/projectnumber... whereas GEOPAK seems to require "pw:\projects\projectnumber..." when we select it. GEOPAK removes the datasource/documents and changes pw:// to pw:\.
It seems the $(dms_project(_DGNDIR) works well for microstation, but GEOPAK seems to need a different path syntax.

Can you recommend a variable or a way to standardize this definition so we don't have to modify/leave it up to the user to define this setting or worse! leave it to one of us to set this on every project we create?
Understandably, once we set it, it will work for the life of the project, but due to other responsibilities, we want to automate this as much as we can without the possibility of user error.

We noticed when selecting folders manually, Geopak truncates the PW directory . We want to create generic variable definitions for paths in our workspace like defining "_USTN_PROJECTDATA = $(dms_project(_DGNDIR))4-0-Production/4-01-Drawings/" and then using $(_USTN_PROJECTDATA) for our Geopak variables.

$(dms_project(_DGNDIR) creates the pw://[datasource]Documents/projects/projectnumber... whereas GEOPAK seems to require "pw:\projects\projectnumber..." when we select it. GEOPAK removes the datasource/documents and changes pw:// to pw:\.
It seems the $(dms_project(_DGNDIR) works well for microstation, but GEOPAK seems to need a different path syntax.

Can you recommend a variable or a way to standardize this definition so we don't have to modify/leave it up to the user to define this setting or worse! leave it to one of us to set this on every project we create?
Understandably, once we set it, it will work for the life of the project, but due to other responsibilities, we want to automate this as much as we can without the possibility of user error.

you cannot mix microstation variables with geopak variables. you can define it anyway you want but the variable syntax needs to be valid

is there a geopak variable to pull automatically a path similar to dms_project(_DGNDIR)? Or would we have to include this variable on every project and hard path it to each individual project?

what does that variable do? you can set the geopak project manager project to be set, geopak always uses the dgn directory as the default working directory unless you specify otherwise.

dms_project(_DGNDIR) sets the PW directory path where the managed workspace is applied in the PW format. Thanks to Travis Wollet, we used the $(LastDirPiece (DMS_PROJECT(_DGNDIR))) definition to help us set another set of variables to account for the syntax change between MicroStation/PW and GEOPAK.
We're currently using GPK_PROJMGR_PROJECTDIR and GPK_FORCE_PROJMGR_PROJECTDIR = 1 with great success so far. We're going to start implementing this for our other variables we want to manage on a project to project basis.

Thanks!