Revit 2017 rebar container problem

Revit 2017 rebar container problem

Anonymous
Not applicable
1,312 Views
4 Replies
Message 1 of 5

Revit 2017 rebar container problem

Anonymous
Not applicable

Hi!

I have some problem with migrating from Revit 2016 to 2017 with RebarContainer. There is new function of RebarContainer in Revit 2017: new property PresentItemsAsSubelements. I need specifies container as single object as it was in Revit 2016, but when I set PresentItemsAsSubelements = false Rebar container specifies as one random item of this container in revit 2017. Revit 2016 specifies it like RebarContainerType and I can select containers using schedule in revit 2016. In this file I create container with PresentItemsAsSubelements = false and its copy of rebars. There is schedule represent this problem. In Revit 2016 I don't have this problem. Now i have wrong schedule. Maybe i do something wrong?

You can see in in difference of Type name, when you select it in work area and how it displays in schedule.

container.PNG

0 Likes
1,313 Views
4 Replies
Replies (4)
Message 2 of 5

jeremytammik
Autodesk
Autodesk

Dear Artur,

 

Thank you for your query and posting here to the public discussion forum.

 

Just to keep track of things, the corresponding ADN case number is 12325126 [Schedule of Rebar Container].

 

I discussed this with the development team, and they say:

 

The PresentItemsAsSubelements variable was introduced in Revit 2017 to enable API users to create 3D rebars that are represented in schedules as one single rebar. The rebar is defined on a plane, and 2D rebars can be concatenated to obtain 3D rebar.

 

  1. API user creates in RebarContainer multiple connected rebars that represents 1 rebar in a space.
  2. API user sets PresentItemsAsSubelements to false.
  3. API user sets parameter overrides related with count, length, etc. of the rebar.

 

If API user sets PresentItemsAsSubelements=false, it is the responsibility of API user to set correct geometry and parameters of RebarContainer items so that RebarContainer represents 1 rebar.

 

I hope this clarifies.

 

Best regards,

 

Jeremy



Jeremy Tammik
Developer Technical Services
Autodesk Developer Network, ADN Open
The Building Coder

0 Likes
Message 3 of 5

Anonymous
Not applicable

But problem is element Type. It represent in schedule as one of Rebar container item in Revit 2017. In revit 2016 it represent as Rebar Container type. You can see it on my screenshot. Instance parameters not a problem. I use parameter overrides as it was before. But I need Rebar Container type in schedule as it was in Revit 2016. You can try to get Type name in schedule in revit 2016 and 2017 with PresentItemsAsSubelements=false and you will get differnt results.

It is same file on screenshot and schedule and different results represending this problem. How can i get result of Revit 2016 in Revit 2017 using type parameters?

Container 2017.PNGContainer 2016.PNG

0 Likes
Message 4 of 5

jeremytammik
Autodesk
Autodesk

Dear Artur,

 

Thank you for your update and further details.

 

I discussed your explanation with the development team, and they say:

 

Currently RebarContainer (Rc) is not schedulable. Only its content is schedulable: the RebarContainerItems (RcItems) representing Rebars.

 

Why Rc is not schedulable:

 

Rc has Rebar category - as its sub-elements: RcItems. So if Rc have 3 RcItems (rebars), in the schedule only sub-elements should be presented. We do not need in the schedule additional row for the Rc.

 

PresentItemsAsSubelements=false means that Rc returns 1 sub-element representing whole content of the Rc.

 

Rc have different type than its RcItems. RcItems has the same type as Rebars because we need to have common schedule for RcItems and Rebars so RcItems and Rebars should have the same parameters, types.

 

Rc used to be schedulable. Currently it is not possible to make them schedulable – it is hard coded.

 

I hope this clarifies.

 

Best regards,

 

Jeremy



Jeremy Tammik
Developer Technical Services
Autodesk Developer Network, ADN Open
The Building Coder

0 Likes
Message 5 of 5

Makarov_d
Enthusiast
Enthusiast

Arthur, the screenshot below is the 2016 version?
It turns out in version 16, you could count the number of containers in the standard way and in 2017 this option was excluded?

 

Артур, скриншот ниже это 2016 верси?

Получается в 16 версии можно было посчитать кол-во контейнеров стандартным способом а в 2017 эту возможность исключили?

0 Likes