Attribute value for hatch not showing in block

[l.leuce]

Hi,

I have created few blocks of extrusions where I inserted some attributes to show up in the block. I used visibility to have different options for each block. Some of them are working as I wanted but some of them don't bring up the value of the attributes. I attached here an example of one working and want that doesn't work. Can I get some help here please as I am under a huge pressure to get the project ready and don't have too much time to search?

Thank you.

[pendean]

Are your fields referencing the actual block itself? #### simply means the field cannot find its source object.

[l.leuce]

@pendean

Please have a look at the file I attached to my initial post. The source for some filed is a hatch area which is also controlled by visibility, the other source is the value of the attribute connected to the hatch. As I mentioned, some of them are working some no..Can't figure out what is wrong and how to make this work.

Thanks

[dbroad]

I'm surprised that the attributes work at all since they are referencing an object in the block definition rather than in the block reference.

I don't know how to fix the block already placed but if you insert another copy of the non-working block, that reference should work.  It could be that you may have changed the hatch after you built the block and it is referencing a non-existent object.

[Alfred.NESWADBA]

Hi,

you assigned an object to this field that does not exist any more (or was modified in a way so it can't be used any more):

For dynamic blocks it is critical (and not stable as you can see) if you refer to a hatch which is then disabled from beeing displayed by a visibility parameter.

[EDIT] just tried ... made sure all objects are visible in the block, then removed the visibility paramter from the block, exit block.editor, inserted the new block in mdoelspace and the attribute holding the hatch area worked well  [/EDIT]

- alfred -

[l.leuce]

@Alfred.NESWADBA

Thank for all replies. 

So what will be the option to have for visibility id I will be removing it? I would like to have the block represented in different ways while having those properties available. I added the hatch because I need the area of the profile, and also I will need to modify the shape during design process. Any ideas for this case please? 

Thank you!

And I remove the visibility from the block but the area fields/values are still not coming up. I still showing ######.

[Alfred.NESWADBA]

Hi,

>> So what will be the option to have for visibility id 

Maybe to have 2 hatches, one white which is always on (and to get the area) and another grey (as your current, that can be changed in visibility).

Or to create a region instead of the outlines, these also have an area to evaluate.

- alfred -

[dbroad]

If the hatch never changes size, get rid of the field. In the attribute default value(of a working field), right click on the field and choose convert to text. Do the same for the formula field.

[l.leuce]

It has to be something else that has been proposed/discussed here. I convert to text but is still coming up as #####. And I do not want to go to regions as I have to often modify the shape, therefore areas and I need to get those areas/weights somehow collected through dataextraction. And how is possible some of the blocks to work and some of them not. It has to be something there..

So my whole scope of work here is the have the profiles(extrusions) created, after them we revise them and then collect the areas, weights for cost purpose and tooling design.I also want to have these extrusions different appearance based on the views I am using them: assembly , detail views and so on..Hopefully this will help to get an idea on how to have this work.

Thank you!

[Alfred.NESWADBA]

Hi,

>> Hopefully this will help to get an idea on how to have this work.

Have you seen my suggestion about 2 hatches?

- alfred -

[dbroad]

In the block editor, edit the attribute definition of the dynamic block definition. Right click on the field and choose "convert to text".  Since the value is only the default value, you will never get the value back in block references merely by redefining the block or synchronizing attributes.  But any block you add in the future will have the correct default value.  Unless your drafter overrides that value, it will be correct.