Submitted by WayneK on 2015/12/18 20:09
1) I created a new grid
2) I went to the grid management list and found there were three grids listed with the same name I just created.
3) Thought maybe I'd previously created the extra grids and forgot about it. So I deleted two of them.
4) Went on to create another grid.  This time I verified there were no existing grids with this name. Again, three grids showed up in the list. 
5) I went back to check the previous grid and found that it was gone altogether.  When I deleted the two "extra" grids it deleted all three of them.
 
Here's what I'm seeing after creating a new grid:
 
Has anyone else seen this, or can figure out what I might be doing wrong to cause it? I've created quite a few grids and haven't run into this before.
 
Update: I restarted InfoQube and the grid I just created (that was showing in triplicate) disappeared just like the first one.  I'll keep trying to create grids to see if this behavior continues.
 
Thanks,
Wayne rel62
 

Comments

Here's what I'm seeing.  I create the grid:
 
 
Then I go to "Manage Grids".  Note that new grid is listed three times at the bottom.
 
 
I closed the grid list, did some other work, and returned later.  Now the list is correctly showing only one new grid (and it also has restored the other grid that had disappeared earlier).  Maybe it's not a problem.  Is it normal to first show duplicates like this?  Confusing.
 
 
Wayne
 
 
 
 
 
 
 
 
 
Wayne
Win 7, 64 bit Cyberpower Model 1, C Series (2011) 16 GB RAM
27" Samsung S27A350H, 24" ASUS VW242H  1920x1080

I remember experiencing something similar and think it was usually resolved just by closing and reopening, I don't think there are really 3 grids, it's a bug of some type and each line just represents the same grid.  I think that's why when you deleted two of them the other one disappeared, you could probably have even deleted one and the other two would have disappeared.
 

WayneK

2015/12/18 21:30

Permalink

David,
 
Yeah, I think that's probably right.  Looks like it's best to just ignore it. 
 
Wayne
 

Well... that one took quite a bit of searching in the code to see what could cause it !!!
But I'm happy to report that it is fixed in v63 !