Hey @athasanka ,
A similar issue was reported where a persistent field is added to the CustomerInfo entity configuration. Thereafter, the field was added to the Sale> Customer> Customer page through the page designer and the changes are not saved when toggling values. The issue is planned to be fixed in 25R1 EA.
However, I am unsure how the changes are allowed to be saved in one page (i.e. Work Task debrief) and doesn’t work the same in another page.
Could you try using the ‘Edit’» toggle the button» ‘Save’ the change? This the workaround used at the moment.
Hey @athasanka ,
A similar issue was reported where a persistent field is added to the CustomerInfo entity configuration. Thereafter, the field was added to the Sale> Customer> Customer page through the page designer and the changes are not saved when toggling values. The issue is planned to be fixed in 25R1 EA.
However, I am unsure how the changes are allowed to be saved in one page (i.e. Work Task debrief) and doesn’t work the same in another page.
Could you try using the ‘Edit’» toggle the button» ‘Save’ the change? This the workaround used at the moment.
Thanks for your reply.
Yes, it seems an odd issue. Given that that the changes on the other fields in the same group get saved automatically. Enabling edit mode doesn’t have any effect - it simply doesn’t recognize the field - Task Chargeable has been changed at all.
Can you think of any attribute why this changes on this field is not recognized, but all the neighbouring fields it does?
Note that WorkTaskDetails is bound to the entity MyAssignementEntity while your group is connected to WorkTaskEntity. If the WorkTaskEntity is a pure subset of MyAssignementEntity this would work. But I guess that your problem here is that your custom attribute is added t WorkTaskEntity but does not exist on MyAssignementEntity.
Note: It is typically wrong to add a group to a parent where the group is not bound to the same entity as the parent. As I said, it might work in the cases where you have different (additional) views for the same entity. But in general, this is not correct, and you should not expect that to work.