Currently, we are not explicitly populating values into synchronized custom attributes during project synchronization. As a result, if some AYON folder attributes are left unset, they will naturally inherit values from their parent folders.
This leads to SG showing no value and appearing empty. To address this issue, we need to ensure that hierarchical values are resolved during project synchronization.
We should explicitly set default values for synchronized attributes and, during the reverse synchronization of attributes from SG to AY, we must verify if values are inherited hierarchically. If they are, we should ignore them to prevent any unintended local entity overrides.
Currently, we are not explicitly populating values into synchronized custom attributes during project synchronization. As a result, if some AYON folder attributes are left unset, they will naturally inherit values from their parent folders.
This leads to SG showing no value and appearing empty. To address this issue, we need to ensure that hierarchical values are resolved during project synchronization.
We should explicitly set default values for synchronized attributes and, during the reverse synchronization of attributes from SG to AY, we must verify if values are inherited hierarchically. If they are, we should ignore them to prevent any unintended local entity overrides.