> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gocrisp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Planogram Library

> Provides a way to quickly create a planogram library using a batch of floorplans as a source.

This automation allows users to create a Planogram Library that can be opened and used with Floor Planning. The planograms
for the library can be collected from one or multiple floorplans.

## Why you would use this feature

Using a Planogram Library supports consistency and accuracy for planogram records. Creating the library can often be
time-consuming, but this automation allows you to quickly make a new library and fill it with planogram records from
your existing floorplan(s).

## Feature Options

### Where do you want to save your new library?

Select the location where the new library file will be saved. The existing file will be overwritten if a library already exists with that filename.

> [!NOTE]
>
> The Access database and the library file will be created in the same folder as the library file. The Access database file and Data Source file will have the same name as the library file but with extensions of MDB and DSN, respectively. The existing file will be overwritten if these files already exist with that filename.

### What makes your planograms in your library unique?

The planogram primary key is what is used in the library to make it unique.  When this library is created with the use of MissionControl, Floorplanning will set the default Primary Key to ID.

If you need to change this ID, you will need to go into the **Planogram Library Properties** within Space Planning itself and update those properties to suit your needs. These settings are not found in MissionControl.

**ID** forces all planograms in the library to have unique IDs. **Name** forces all planograms in the library to have unique
Name. **ID+Name** forces all library planograms to have unique ID and Name combinations.

> [!WARNING]
>
> Library files contain specific information based on the folder they were created in. Moving the library, Access database or Data Source files to a different folder can invalidate this information and prevent the library from
> being usable. It is recommended to keep these files where they are created and not move them. When creating libraries to share with others, selecting an initial folder location that others can also create on their PC is recommended.
