Pavel Aleksandrov
Pavel Aleksandrov
Test cases: 1. There are no "Dynamic Attributes add-on", but there is "Search add-on" 1.2. There are no configured indexes for "Search add-on" 1.3. There is search indexes but @DynamicAttributes...
See io.jmix.dynattrflowui.impl.factory.DynAttrPropertyFilterComponentGenerationStrategy#createComponent. It doesn't support case when context.getProperty() value is path with dot delimiter but not a single attribute name.
Being suggested solution is to hide dynamic attributes from generic filter if they are not at the first level of the objects' hyerarchy.
The suggestion is to store not applied changes in a separate tables.
The loading of the attributes' values is implemented in io.jmix.dynattr.impl.DynAttrManagerImpl#findValuesByEntityIds
The solutions might be 1. To delete the attribute values when the attribute owner have been deleted. 2. No to load all values. To take into a part current the...
I moved it to "draft" to add specific logging checks in tests.
The problem is not only cousing with not using designated method. The problem is with not setting orderNo field of "CategoryAttribute" entity.
The problem is with the following code But
Take into account to check the dynamic attributes indexing with the Search add-on.