Derived field updating

[dkeeley]

Hi,

A quick question. I have an item that has a field that derives its value from a field in another workspace. The derived field populates correctly when I select a new item from the linked pick list. So far so good. However, when the value of the field in the original item is changed - it does not automatically update in items where the value of the field is displayed as a derived value. Is this normal behavior?

Thanks for your help,

David.

[dkeeley]

OK,

So I checked the Help and according to this I shouldn't be seeing what I am seeing. Am I missing something? Is there a time lag between the field in the parent item being updated and these changes being reflected in derived fields?

http://wikihelp.autodesk.com/PLM_360/enu/Help/Help/0040-Administ40/0049-Setup49/0050-Workspac50/0053...

David.

[dkeeley]

Some images attached.

[JohnCHill]

Hi David,

If you have a record open and make a change to a Derived Field Source you do need to refresh the record page to see that change.   I've seen the field automatically update after editing a record or refreshing the page.

Regards,

John Hill

[dkeeley]

Hi John,

Thanks for the message.

However, I've already tried refreshing, logging out and back in, and leaving overnight - its still not updating.

David.

[JohnCHill]

I've tested and I cannot recreate this issue with the Derived Field.  Can you try deleteing and recreating the Derived Field in the workspace?   Also send me a screen shot of the Test field configuration.

Thank you.

John

[dkeeley]

Hi John,

Can I give you a log on to our tennant? If so please email me and I will send you the details.

Thanks,

David.

[JohnCHill]

David,

I can duplicate this issue using the BOM Picklist as the pivot field.

I will esculate this issue to the PLM 360 Development Team.

Thank you for bringing this to my attention.

Regards,

John

[dkeeley]

Thanks John. How long do you think it will take to rectify?

[JohnCHill]

This issue will be prioritized by the Development Team and fixed in a future update to PLM 360.  Since the issue was just esculated it is hard to say at this point when a fix will be in place.

Regards,

John