Product(s):	OpenBuildings Designer
	Version(s):	CONNECT Edition
	Environment:	N/A
	Area:	Datasets and Content
	Subarea:	Configuration

In the configuration scenario where an organization takes ownership of a regional dataset and locates it in a Custom Configuration alongside the Organization and WorkSpaces folders, a small configuration change is required.

The path to the Dataset root folder in a Custom Configuration is set as follows (using W:/OBD/Configuration/ as an example location):

Update 6 and Earlier

On the C:\ drive set the location of a Custom Configuration in the ConfigurationSetup.cfg file, [General] section

_USTN_CUSTOM_CONFIGURATION = W:/OBD/Configuration/

This will result in _USTN_CONFIGURATION being resolved to W:/OBD/Configuration/

In the root of the Custom Configuration, in this example: W:/OBD/Configuration/, modify WorkSpaceSetup.cfg (this can either be a copy of our delivered file, or simply a new file with that name containing only the required statements).

Unless other statements are appropriate in this file, all that is needed are these two lines:

%undef _TF_WORKSPACEROOT
_TF_WORKSPACEROOT =  $(_USTN_CONFIGURATION)

The first line clears the existing definition of _TF_WORKSPACEROOT, the second applies the required definition.

Without the %undef statement the application will always use the delivered datasets.

Notes:

• Do not include a copy of ConfigurationSetup.cfg in this location, it should only exist on the c: drive.
• This file must be called WorkSpaceSetup.cfg.

Update 7 and later

In Update 7 this behaviour is reversed:

Use datasets in Custom Configuration:

Simply defining a Custom Configuration location will make OBD look for the Dataset root in the Custom Configuration (and to be clear, this only applies when a Custom Configuration is defined). In that use case existing instances of the statements described above can be omitted from WorkSpaceSetup.cfg.

To use delivered datasets on C:\ drive:

If you have a Custom Configuration that does not include a Datasets folder OpenBuildings Designer Update 7 will not find the Datasets folder on the C:\ drive without this small configuration change.

To use the delivered Datasets on the C:\ drive; the statements in the WorkSpaceSetup.cfg at the root of the Custom Configuration will need to be as shown in red below:

#----------------------------------------------------------------------
# Support for ProStructures Application Integration
#----------------------------------------------------------------------
# Update 7 and later to use delivered datasets
%undef _TF_WORKSPACEROOT
_TF_WORKSPACEROOT : $(_USTN_INSTALLED_CONFIGURATION)
TF_DATASETS : $(_TF_WORKSPACEROOT)Datasets/
TFDIR : $(TF_DATASETS)$(TF_DATASETNAME)/

This includes the default statements needed to enable integration with standalone ProStructures applications.