Macro System Help With Globals

[Renerabbitt]

I have a system that designates a global macro value based on it being in the schedule number 1 position, as in a note schedule where the note checks schedule number and defines the macro based on a custom field within the note. This macro in its current state can only be initialized by opening the row object or directly opening the object. Is there someway to get this to work where I do not need to open the row object, so that as soon as I move something into schedule 1 position it initializes? The value updates but they macro will not update unless the object is opened

[Joe_Carrick]

I have a similar problem with a schedule with a macro that generates an error until one of the row items has been opened and closed.  This is a rather complex macro accessing some custom field values.  I haven't found a way to solve it.

 

I've asked Chief to provide a tool that would update on demand but haven't received a fix.

 

In your case I would check to make sure some other process isn't messing with the global value(s).

[Renerabbitt]

3 minutes ago, Joe_Carrick said:

I have a similar problem with a schedule with a macro that generates an error until one of the row items has been opened and closed.  This is a rather complex macro accessing some custom field values.  I haven't found a way to solve it.

 

I've asked Chief to provide a tool that would update on demand but haven't received a fix.

the basis of mine:
 

$wall_framing2 ||= '2"X4" DF#2 @ 16" O.C.'



# UPDATE GLOBAL VARIABLES BASED ON 'schedule_number' AND 'type'

begin

if schedule_number.include?("01") && type.downcase.include?("wall framing")

$wall_framing = custom_fields["Macro Input 1"]

end

and yes its very frustrating

[Joe_Carrick]

I really think this is a problem with macros in custom fields.

[Renerabbitt]

15 minutes ago, Joe_Carrick said:

I really think this is a problem with macros in custom fields.

same problem if you use component_code

[Joe_Carrick]

I had a problem with direct access/assignment of macro values in calculations.  By first assigning the macro result to a variable and then using the variable in the calculations it worked perfectly.  I'm going to experiment with that technique to see if it solves my problem.

 

[Renerabbitt]

5 minutes ago, Joe_Carrick said:

I had a problem with direct access/assignment of macro values in calculations.  By first assigning the macro result to a variable and then using the variable in the calculations it worked perfectly.  I'm going to experiment with that technique to see if it solves my problem.

 

thats essentially what I am doing. I am assigning an initial value in leau of have a nil condition or error, but that doesnt change the fact that I still need to open the row object to initialize a change based on schedule number unfortunately.
Same thing happens if you use a text box to reference a schedule number from a note, you still have to open the text in order for it to initalize a change even though the text box itself confirms the change before you ever open it when the schedule number is changed. So something with the way it is accessing the info

[Alaskan_Son]

This has to do with the way schedule dependent attributes are handled differently inside schedules than they are in the plan.

 

I can definitely help you get this working like you want if you want to set up a one-on-one consultation session...

 

If you were subscribed to my Mailer though, you probably wouldn't have had to