BuildPlus has the ability to import projects from BPI (BuildPlus Import) files, which are turn created via exporting and can also be found in each project's error files folder. Particularly for large batches of imports you may find it helpful to use the command line.

Importing single BPI files

To import a BPI file you need to specify at least the file to import and the BuildRoot to import into.

/importbpi

• Specify a single BPI (BuildPlus Import) file to import.

/importroot

• Specify the BuildRoot to import the project into.

 "C:\Program Files\GMCL\DBDOC\Programs\BuildPlus" /importbpi "C:\DBDOC_BUILDS\Project07\Project07.bpi" /importroot "D:\DBDOC_BUILDS"

Specify name for single BPI import

/importproj

• When importing a single BPI file from the command line, you may optionally specify a new project name. Without this option BuildPlus will automatically generate this based on the BPI filename.

 "C:\Program Files\GMCL\DBDOC\Programs\BuildPlus" /importbpi "C:\DBDOC_BUILDS\Project07\Project07.bpi" /importroot "D:\DBDOC_BUILDS" /importproj "Project07_copy01"

Import multiple BPI files

/importbatch

• Import a batch of BPI files, as defined by a CSV file. BuildPlus expects three columns: path to the BPI file, root to import into, and optional project name. If you are not specifying the optional project name, the second comma is still required. You can create this in a spreadsheet program or via a text editor.

For both previous importing examples the CSV file would look, when viewed as plain text, like:

 "C:\DBDOC_BUILDS\Project07\Project07.bpi",D:\DBDOC_BUILDS,
 "C:\DBDOC_BUILDS\Project07\Project07.bpi",D:\DBDOC_BUILDS,Project07_copy01

To import, specify the path to the CSV file.

 "C:\Program Files\GMCL\DBDOC\Programs\BuildPlus" /importbatch "C:\DBDOC_BUILDS\Project07\Project07.csv"

See also

• Running BuildPlus with command line switch /build
• Running buildalls with command line switch /buildall
• Using command line switch /MOC
• Using other command line switches