Hotlinked Element:Expression cannot be evaluated

[Anonymous]

Hello All,
I wish and hope that you are well and healthy!

I wanted to create some schedules based on objects. I have created Expression based properties.
They output only if objects are native and not hotlinked.
AC outputs schedules of hotlinked elements but does not output values of these expression which are referring to hotlinks. Please see the uploaded image.
Is there any alternate?
Kindly replay ASAP.
Thanks in advance.
Regards,

[Laszlo Nagy]

Would you do a short experiment so we can see if the Hotlinked Module is indeed the source of the problem?:

1. Save the Project File, then save a copy of the Project File using "File > Save As".
2. In this copy, break the Hotlink that contains those Zone and elements, effectively incorporating its contents into the Project File.
3. See if the Expression is now properly evaluated.

Another question is, are these Hotlinked Modules nested, so there are Hotlinked Modules within the Hotlinked Modules? (That may or may not be relevant.)

Please let me know the results.

[Anonymous]

Hello LaszloNagy,
Did experiment which you suggested.

Please go through attached image.
The expression based property works after breaking the hotlink.

Shouldn't be so.
Kindly provide solution.

Regards

[Laszlo Nagy]

Unfortunately, I cannot provide a solution because this may be a bug. As you stated, when the element is in the host file, the Expression returns a value, when the element is in the hotlinked module, the Expression does not return a value.
So, all I can do right now is report it to GRAPHISOFT as a possible bug.,

[Laszlo Nagy]

Actually, I was thinking something else: does the Property return a correct value (is it correctly evaluated) when you use it in a Label?
And does it return a correct value when you use it in a Schedule?

[Anonymous]

LaszloNagy,

It doesn't return anything in a schedule.

This is an important feature in calculations so please report.

Thanks,

[Laszlo Nagy]

Yes, I did report it.
You can also report it through your local reseller.

[Minh Nguyen]

Hello,

Thank you very much for the question!

I tried to reproduce the issue from scratch using the latest update (4018) for Archicad 24 INT. Same as you, I can see that the expression cannot be evaluated if it is placed in a module. But, the expression does work with labels and schedules, as can be seen in the screenshots attached below.




This makes me wonder: does the Evaluate function work for you in previous Archicad versions?
Looking forward to hearing from you!
Best regards,
Minh

[Anonymous]

Minh Nguyen,
I was expecting that Graphisoft would rectify the bug after reading these posts.
But when I checked the function today I realized that the problem exists.
Now I have Ver 24 Build 5000.
Is it necessary to report through my reseller?
Narendra
18/04/2021

[Barry Kelly]

Narendra wrote:
Is it necessary to report through my reseller?

It certainly helps.
It can give the problem a little more importance when it comes from multiple sources.
Even more so if it comes from multiple users.
What is that old saying - "The squeaky door gets the oil".

Barry.

[Minh Nguyen]

Dear Narendra,

Thank you very much for your comment!

Unfortunately, as I mentioned previously, the expression cannot be evaluated if it is placed in a module. The Evaluation function also gives you this notice, if you look at the screenshot in my previous answer. I believe this is a limitation with the Evaluation function, as it works more like a preview to test the function.

I am very sorry for the inconvenience! I highly suggest reporting this through your local reseller in order to ask for higher priority.

Best regards,
Minh

[Andreas _kerlund]

Hi!

Saddly I can report that the problem still exist in Archicad 25. In autotext labels as well as in schedules.
We had the same problem in AC23. It makes me sad when bugs don´t get fixed over several versions....

[Minh Nguyen]

Hi Andreas,

Thank you very much for your comment!

Previously, I did some experiments with a custom expression, and the result is that the expression works well in labels and schedules. May I ask for the expression you are using that does not work in labels/schedules for in-house reproduction?

Looking forward to hearing from you!
Best regards,
MInh