​Defining a custom library

Creating an Excel file in the Custom Content Library Configuration window

Prerequisite

A folder structure containing all content(.xml, .xlsx, .rfa, and .png files), see the Folder Structure Suggestions section below.

Creating a library from a folder structure

This method of generating the .xlsx file uses the file structure to organize content. The folder name(s) within the directory containing the .xml are used as the family's category and any sub-folder(s) are used as the family's sub-category.

  1. If the eVolve Family Browser is not already displayed, from the ribbon, click the eVolve Mechanical tab and click Family Browser from the Utilities panel.
  2. From the eVolve Mecahnical Family Browser, click Custom Library Settings.
  3. From the Custom Content Library Configuration window, verify the path in the Library Location dialog is correct and click the Create Definition File button.
  4. From the Create Definition File window, select the desired option and click OK.
    1. Use root folder name - the Sub-Category will only display the name of the folder containing the .rfa files.
    2. Concatenate folder names with separator - if the .rfa file is contained withing multiple sub-folders, the folder names are stringed together and used as the family's Sub-Category name.
  5. From the Please Confirm window, if the displayed path is correct, click Yes.
  6. From the Build Library Definition File window, enter or select an existing name in the Target File Name menu and click OK. The .xlsx file is generated.
  7. From the Notice window, click OK.
Once the Excel file is created, the cell values may be modified to customize the filter/group/sort/search parameters.
Folder Structure Suggestions

Suggested folder structure Option #1

This method of generating the .xlsx file uses the file structure to organize content. The folder name(s) within the directory containing the .xml are used as the family's category and any sub-folder(s) are used as the family's sub-category.

  • Custom Library - a folder containing the .xml, .xlsx, and content folder(s)
    • content - folder(s) containing .xml, .xlsx, "Category" and "Sub-Category" folders, .rfa(s), and .png(s)
      • Category_A - contains .rfa and .png files
        • Sub-Category_1 - contains .rfa and .png files
      • Category_2 - contains .rfa and .png files
        • Sub-Category_A - contains .rfa and .png files
          • Sub-Category_2B - contains .rfa and .png files

Folder names do not need to match the folder names in the above suggested folder structures

Suggested folder structure Option #2

This type folder structure is intended for users who wish to add all content into one folder then modify the Excel file to further filter/group/sort/search.

  • Custom Library - a folder containing the .xml, .xlsx, and the content folder
    • content - a folder containing the .rfa(s) and .png(s)

Creating an Excel file from a Revit project

Prerequisite

A project containing each type of every family that will be contained within the custom library.

To easily create a list of all families and types, a Revit project containing an instance of each family and type is required. This method of generating the .xlsx file uses the values specified in the eVolve_CategoryId and eVolve_SubCategoryId cells to organize the content. The following steps will create a text(.txt) file containing the necessary information needed to create the custom library .xlsx file. The exported text file may be opened in Excel then saved in the .xlsx file format. While the Family and Types are automatically pulled from their respective .rfa files, the other shared parameters listed in the Excel Template break-down section below must be added to the project or families in order to populate the rows.

  1. While in a project, from the Properties Browser expand Multi-Category in the Schedules section, open eM_Family_List.
  2. From the ribbon, click File, click Export, click Reports, and click Schedule.
  3. From the Export Schedule window, navigate to the desired location to save the file, specify a name in the File Name dialog box, and click Save.
  4. From the Export Schedule window, select desired options and click OK. A .txt file is generated.
  5. After the text file is created, open the file in Microsoft Excel and save the file in the .xlsx format.
The eM_Family_List schedule is contained within the eVolve Mechanical_Template_20xx.rte located in - C:\Program Files\eVolve\eVolve Mechanical for Revit 20xx\Resources
Either folder structure example listed above may be used with this method.

Excel Template break-down

Custom libraries are defined in an Excel file (.xlsx) and must contain the following headings:

Each Family and Type must be listed separately in the .xlsx file
The Family name and Type displayed in the Excel file must match the Family and Type displayed in the .rfa file.
  1. Family - the cell value must match Family name contained within .rfa file.
  2. Type - the cell value must match Type contained within .rfa file.
  3. eVolveTypeDisplay - Optional field. The cell value will display on the card, if a value is not specified, the card will display the cell value of the Type column.
  4. File Path - cell value equals the main root folder containing all content.
  5. eVolveCategoryId - the cell value equals the share parameter the family is grouped by.
  6. eVolveSubCategoryId - the cell value equals the share parameter the family is grouped by.
  7. eVolve_UnitofMeasure - Optional searchable field.
  8. Manufacturer - row value equals the share parameter the family is grouped by.
  9. Model (optional) - currently not utilized
  10. eVolve_Hardware_Finish - Optional searchable field.
  11. eVolve_Hardware_Size - Optional searchable field.
  12. eVolve_Hardware_Type - Optional searchable field.

Once the Excel file is created, the cell values may be modified to customize the filter/group/sort/search parameters.

Click the following link to manually populate a blank template - Blank Excel Template

Relevant Articles

Creating a custom library

​Adding a custom library to the eVolve Family Browser

Overview of the eVolve Family Browser


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)