Skip to Content (Press Enter)
Back to Ideas
1
Like
Follow Idea
Auto Refresh Aggregate when new attribute is added
267Views
5Comments
Out of scope
Aggregates & Queries

Whenever we add a new attribute to an entity and that entity is being used in an aggregate, it's always required to delete the entity from the aggregate and add it again to display the new attribute. It would be very helpful if it was only necessary to refresh the dependencies to display newly added attributes. 

02 Mar 2023
Copy link to comment

Hi @André Vieira ,

that's not what happens when I try it, after adding an extra attribute, it becomes immediately available in the aggregate, only thing is, it is hidden (a little grey number above preview data) so you'll still need to click on that to show it.

I have tried while having an aggregate open for design and with opening aggregate after the change, both with an entity in own as an entity from other module, never had the need to delete the entity.

02 Mar 2023
Copy link to comment

Hi @Dorine Boudry 

try to perform joins with other entities and test the same scenario again, please. 

02 Mar 2023
Copy link to comment

nope, also works with joins, joins entirely inside own module, joins entirely in consumed module, joins from own to consumed module.

After possibly refreshing dependencies if new attribute was added in producer module, it always appears immediately in my aggregate as a hidden column.

Only thing i can come up with, is maybe version of service studio ? mine is Version 11.53.41 / Build 62020 

02 Mar 2023
Copy link to comment
2026-02-26 06-29-24
Rahul
 
MVP

Hi @André Vieira ,

I tried what you mention , but this is not a case as @Dorine Boudry already mention when we add new attributes it shows as hide column.


Regards 
Rahul 

02 Mar 2023
Copy link to comment
Changed the status to
Out of scope

Not an idea. Firstly it works as expected on Service Studio of other community members including me. If you still experience this problem it might be related either to your Service Studio version or your computer, you should report it via the Feedback button in Service Studio as a bug.

03 Mar 2023
Copy link to comment