twitter youtube facebook linkedin email
Connect with:

BIM 360 Release Notes

BIM 360 Field web release – restore custom properties

Krystian Macek
June 11, 2019


  • Restore checklist custom properties
  • Equipment Changes report improvements
  • Link existing checklists to a task
  • View number of linked open checklists in Tasks grid

Restore checklist custom properties

Mistakes happen!  From time to time a project admin may delete a checklist template custom property not realizing that this will also delete that custom property and its value for any previously completedchecklist.  To help self-remedy this situation, we haveadded the ability for project admins to restore deleted checklist template custom properties along with their values.

To delete a custom property:

  1. Click Project Admin > Checklists > Custom Properties.
  2. Select a custom property checkbox.
  3. Click Delete.

To restore a custom property:

  1. Click Project Admin > Checklists > Custom Properties
  2. Select a custom property checkbox
  3. Click Restore.


Additionally, if a checklist template custom property was deleted but contained a value, this property will show up on existing checklist as grayedout.

Equipment Changes report improvements

We’ve improved the formatting of Equipment Changes in Excel and CSV format by removing the page header and footer that were visible in PDF output

Link existing checklists to a task

In some cases, a checklist is filled outside of a task and there is a need to re-link them bothtogether.  Project Admins now have the ability to link one or more checklists to a task after a checklist was filled out.

  1. Go to Checklist
  2. Select one or more checklists
  3. Click More Actions > Select Link Task

View number of linked open checklists in Tasks grid

In the Tasks, we’ve added the ability to view the number of linked open checklists.  To enable two new columns:

  1. Tasks grid
  2. More Actions
  3. Customize View
  4. Select # Checklists and #Open Checklists

MktoForms2.loadForm(“//”, “572-JSV-775”, 2332);

#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
#mktoForm_2332 > div.mktoButtonRow > span > button{
color: #fff;
background-color: #1858A8 !important;
background-image: none !important;
border: 0px !important;
#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoLogicalField.mktoCheckboxList.mktoHasWidth.mktoRequired, #mktoForm_2332, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField
{width: 100%!important;}
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoOffset,#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
display: none;
width: 75%!important;
width: 84px!important;
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol{
margin-top: 10px;
width: 100%;

Subscribe to email digests.

Featured Links

Krystian Macek


View by:
Most Recent Oldest

    That’s really good point. thanks Krystian. My question why we could’not export Custom parameters as an excel column? While we want to export Equipment Report (List by Type) we could not get our custom parameters as an excel column. It is driectly export PDF view to the excel. So that we could not look up our parameters easily. (Because it is not in the column) May be you have a suggestion.Thanks again…

    1. Krystian MacekKrystian Macek (Post author)

      Hi Umit, custom property export is not yet implemented in excel exports. We will consider this as an enhancement request. Thank you for your feedback.