You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open a new blade which has different grid settings and change grid settings in that blade.
Close new blade, click "Refresh" on the old blade. The grid in old blade with load settings of the previous blade.
When we refresh data, Uigridutils uses bladeNavigationService.currentBlade to get settings of the grid. And when we close blade, bladeNavigationService.currentBlade points to the closed blade.
It seems that the issue can be fixed in bladeNavigation.js:
if (blade.parentBlade && blade.parentBlade.isExpandable) {
blade.parentBlade.isExpanded = true;
if (angular.isFunction(blade.parentBlade.onExpand)) {
blade.parentBlade.onExpand();
}
}
Replace the above code with:
if (blade.parentBlade) {
service.currentBlade = blade.parentBlade;
if (blade.parentBlade.isExpandable){
blade.parentBlade.isExpanded = true;
if (angular.isFunction(blade.parentBlade.onExpand)) {
blade.parentBlade.onExpand();
}
}}
The text was updated successfully, but these errors were encountered:
There is a problem when we open couple of child blades (e.g. Catalog->Select category->Select product), and then click on some catalog in Catalog blade. Video with catalog
You can see that because showing called before closing children service.currentBlade is assigned improperly - it is not opened categories blade, but the catalog one (which is the parent of blade closed last).
So we cannot apply this change now. Whether more changes needed here, or maybe you could try to solve the problem other way.
Platform: 2.13.47
When we refresh data, Uigridutils uses bladeNavigationService.currentBlade to get settings of the grid. And when we close blade, bladeNavigationService.currentBlade points to the closed blade.
It seems that the issue can be fixed in bladeNavigation.js:
Replace the above code with:
The text was updated successfully, but these errors were encountered: