topic ROOM_NUMBER vs. Zone Number in Libraries & objects

ROOM_NUMBER vs. Zone Number

adamrendek — Thu, 24 Apr 2014 18:39:56 GMT

I'm trying to push a (previously set) custom parameter into the ROOM_NUMBER field by adding:

PARAMETERS ROOM_NUMBER = [custom parameter name]

into the Parameter Script of a Zone Stamp object so that I can list library parts belonging to the Zones identified by the custom Zone Numbers. I'd like to use the interactive schedule adding the Zone Number from the General Available Parameters. For some reason the

PARAMETERS ROOM_NUMBER = [custom parameter name]

does not populate the Zone Number field even after re-loading the library and updating the zones. Why is that? Why is the same field named differently? (ROOM_NUMBER vs Zone Number). What is the correct parameter to use to populate the Zone Number field?

Re: ROOM_NUMBER vs. Zone Number

Anonymous — Sat, 26 Apr 2014 14:27:59 GMT

Hello,

ROOM_NUMBER is a string, is the pushed
parameter a string as well?

Re: ROOM_NUMBER vs. Zone Number

adamrendek — Sat, 26 Apr 2014 18:22:36 GMT

Hi Juha,

Yes, the pushed parameter is a string. For some reason the Zone Number fields are empty in the schedule, but when I open the individual zones the Zone Number field displays the correct value.

I'm scheduling library parts and I'd like to get their zone relations captured in the schedule, but I still have trouble with it.

Re: ROOM_NUMBER vs. Zone Number

Anonymous — Sun, 27 Apr 2014 09:01:09 GMT

Hello,

Interactive schedules are a bit troublesome.

You might try updating the location only
when the context is settings dialog, floor plan or
3D and avoid updating when context is
calculation. This can be done with global
parameter GLOB_CONTEXT.

Check the documentation for values, for example;
settings dialog GLOB_CONTEXT= 1
floor plan GLOB_CONTEXT= 2
3D window GLOB_CONTEXT= 3
calculation / listing GLOB_CONTEXT= 5

Re: ROOM_NUMBER vs. Zone Number

adamrendek — Tue, 29 Apr 2014 18:23:18 GMT

So. I turned out that the solution was deleting the Zone Number value manually in the zone settings dialogue. Once I did that, the PARAMETERS command was able to populate the field consistently with whatever I wanted it to.