Apparently in Connect update 13 labels do not update when I change Item properties. In older versions this worked correctly.
See attached screenshot. When I change the item property "01-lokaalnaam" from "test" tot "test5" this is not reflected in the attached label.
This makes Update 13 completely worhtless. I have to uninstall it from the workstations on which it is already installed.
I just hope I missed something but I am afraid I did not.
15 plan tweede verdieping.dgn
Luc Dierick
Belgium
We need a Service Ticket for the problem - and I hope, the Product Managers find a way to solve this before U14...
A Report shows the Changes in your Items correct, so they are changed, but not displayed.
Also: The Key-In PLACE LABEL gives "Command not defined for this Application" in U13.
Hi Luc,
FYI:
Development and QA both are working on this issue that has been reported as Defect # 1053229.
We have logged Service Request: 7000957234, Labels do not update and have linked the defect with that.
Thank you for bringing this to our attention.
Best regards,
Henk
Is there any chance to get the fix into the unreleased German U 13 ?
Waiting many months for U14 is not a solution for such a defect.
I agree that waiting months for a solution for this is not really an option....
Testing with Luc's files I can replicate the problem.
However working with another example that uses lookup tables to populate Item Types, Labels update correctly. Maybe this could help in some situations pending the defect being fixed. Please see Item Types - Populating Items using Lookup Tables, I have added a video showing this technique used with Labels, scroll down to the 'Use with Labels' heading to see it.
Using lookup tables allows one Item Type property to drive a whole set of related properties:
Marc
Henk Ligtvoet said:Thank you for bringing this to our attention
Marc Thomas said:Testing with Luc's files I can replicate the problem
I raised the problem some time ago in this thread. You can see that one of your core developers acknowledges this bug.
Regards, Jon Summers LA Solutions
Oh yes, I saw Robert Hook's post, I'm not suggesting otherwise, but possibly the lookup method is not affected in the same way?
(I just wanted to mention that I had looked at Luc's original problem and found the same behaviour.)