Issue
Determining BTCustom Fields Availability for Custom Mapping and Override
Solution
DirSync comes with 35 custom internal fields to be used for various sync profile customization such as Custom Mapping and Override. These fields are called BTCustom1 thru BTCustom35, and some of these fields are being used by default overrides. When DirSync administrator create additional Custom Mapping/Override, it will be important to choose a field that is not used, hence user should utilize the below SQL query to identify those that are already in use.
To run this query, open SQL Management Studio and create a new SQL query, point the SQL database to the desire DirSync Database, enter the query as below:
select DISTINCT InternalField as BTCustomInUse from dirsync_mapping where InternalField like 'BTCustom%'
select DISTINCT FieldName as BTCustomInUse from BT_ViewOverrides where FieldName like 'BTCustom%'
select DISTINCT FieldName as BTCustomInUse from BT_ViewOverrideDefaults where FieldName like 'BTCustom%'
Sample Output
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center