---
title: "Distribute Planned Collar"
canonical: "https://servicedesk.maxgeo.com/space/LogChief/1275232317/Distribute%20Planned%20Collar"
format: markdown
---
As the name suggests, this functionality will be used to distribute planned collars from the MDS to the Configuration Database.

Data from tblDHCollPlanned will be distributed by the **Distribute Planned Collar** tool to tblDHColl and tblDHSurv tables. The columns are selected by mapping screen where you map the columns against each table. By default, LogChief maps few columns. User has a choice to map more or modify existing mappings. This column mappings will be exported with Configuration and other user can import them.

Click on the ***Tools > Distribute Planned Collar****...* menu item in the main window of LogChief

![image](media://a90e7e59-dbf7-4439-980d-03eac7d1a988)

Dataset(s) in the screen above are not related to Filtered DataSets. It displays all available DataSets from tblDHCollPlanned table from MDS. "Distribute Collars" button will be disabled if your configuration doesn't have column mappings.

Click on "Columns Mapping" tab to Add / Modify columns mapping.

![image](media://04d9cc7d-2eed-4bc8-b28e-d7e9d57b455c)

By default, this screen will show the existing columns mapping, if there is any. In some cases you might not have any column mapped e.g. if you have upgraded LogChief from previous versions or you are using existing configuration which was made before LogChief 3.2.0. This functionality is introduced in LogChief 3.2.0 and LogChief will automatically introduce this columns mapping when you are creating new configuration or editing a configuration and it doesn't have any column mapped.

This screen is divided into two sections. In first section, it shows all the columns from tblDHCollPlanned table in the left hand side panel. User can map a column from tblDHColl & tblDHSurv tables against these column. In the second section, it shows dropdown list of all the columns from tblDHCollPlanned table in the left hand side panel. This is very useful as user can map same column, at max 10 times, with different different columns from tblDHColl & tblDHSurv tables e. g. In the screen above, we have mapped Hole_ID column from tblDHCollPlanned table twice, first in "Section 1" & second time in "Section 2" against Historic_Hole_ID column.

This mapping is completely based on user's knowledge and doesn't have any functionality to check datatype of mapped columns or Not Null column checking. So it is user's responsibility to check carefully and map right columns and also map all the not null columns. Mapping wrong columns or missing Not-Null column may result in failed import.

Please test the mappings before exporting the configuration.