InfoQube IM - Community

Submitted by ChrisC on 2016/12/26 16:53

I have items I have input and now don't show. Hoping I can get some help here.

I can see in the Properties pane of the parent I put them in that InfoQube has them as children.

I click on them there and they show in the Scratch grid.

Or if I hoist the parent I can see them where I put them.

How do I get them to show without hoisting or finding them in the scratch grid?

I am befuddled. I'm sure it's a simple solution. I just don't know what it is. Thanks for the help!

Chris

Comments

Hi Chris,

The basic concept is that a grid will show items that meet its filter criteria (which includes the source or "main filter", and the secondary filters). That's it. A grid doesn't really contain items, but merely shows/displays them and will also apply certain fields depending on your configuration.

So you just need to know what filter your grid(s) have, and make sure that the items have data meeting that filter.

Did you look at the help file, the "getting started" section (online is better)? It's not perfect but it gives important indications.

IQ geek

Windows 8.1

CPU: Intel i5 2.6ghz

Hi Chris,

When you view those "missing" items in the scratch grid, checkout the Values section to see all the values assigned to that item. Any of these values can be shown in a grid.

Another reason why your items may be missing is that you've applied a column filter.

Pierre_Admin

IQ Designer

Hello Armando and Pierre,

I am unable to get the items to show on the grid I expect them to be. I have attached 2 screen captures with the items and properties pane.

In the "Original Grid I look for the Items in.jpg" you will see two of the "CKD Files" as siblings. That's because I hadn't realized I'd lost the first one, or at least didn't see it, so I made a second. They both had different sub-items in them as they are stored as separate items. Since taking the screenshots I have merged the subitems.

I have checked all the filters I know how to check, alphanumeric, date, source bar, Grid Filter, none of them are set to filter for anything. And I still don't see the itmes where I should.

What do you suggest I do?

Thanks for your help.

What grid are you trying to show those items in? is it the "S::Locate" grid?

If that's so, it seems to me that your "ckd files" items don't have the "grid-locations" field checked, which is the source of the "S::Locate" grid.

(In any case, your "ckd files" item seem to have only 2 fields with data (item, idmainparent), so one of those would need to meet the source for the grids in which you want them to appear. And since those fields are shared between many/most items, you should probably consider adding some data, other fields, to them to differentiate them from the rest.)

IQ geek

Windows 8.1

CPU: Intel i5 2.6ghz

OK Armando,

That did it. I thought for sure I had looked for the "Grid-Locations" box being checked before. I really do know that much. (-:

I have spent enough time with the program to input a lot of data and most of the time get it to fulfill my basic needs.

I don't understand what I did to lose this data, in the grid I had put it I mean. I hope to be able to master this program instead of being spun around by these kinds of situations.

Thanks so much for setting me straight.

Cheers,

Chris

You *might* have demoted those items at some point (and it could even be that you demoted the items in another grid having the same "source"), and that can delete the source from the item.

This behavior often confuses users — especially in the scenario I just described : when items are demoted in one grid that can affect what's displayed as TLI in another one (with a similar source).

What you can do to prevent that from happening in the future is to make sure that the "keep source fields value when demoting TLI" option in "Manage grids" is checked for most of your grids.

The corollary of turning on that option is that when you’ll display items as a flat list (display mode -> source items), if you do use that feature, you *might* have unwanted items appear as TLIs. But this generally not a problem -- at least not for me! — especially if you use the default display option : “Outline (normal)”

IQ geek

Windows 8.1

CPU: Intel i5 2.6ghz

[quote=Armando]

This behavior often confuses users — especially in the scenario I just described : when items are demoted in one grid that can affect what's displayed as TLI in another one (with a similar source).

What you can do to prevent that from happening in the future is to make sure that the "keep source fields value when demoting TLI" option in "Manage grids" is checked for most of your grids.[/quote]

Demotion was my guess as well and unless I am missing something, I really think "keep source fields when demoting TLI" should be the the "out of the box" IQ default for when new grids are created.

Hi Chris,

I think the key to understanding what is happening is that the !Yo main item appears to be a context parent in the main grid (shown in blue).

Why is that ?
Where was that outline, starting with the !Yo main parent created ?
Was it in another grid or in the current one (S:Locate) ?

As Armando pointed out, to see your CKD Files item, either it has to meet the grid source / filter or a parent in the parent tree has to meet it. In this case, neither of this appears to be true, hence it is shown and this is by design.

I disagree with what other have said that "keep source fields value when demoting TLI" option is the way to go, in fact, in practice it can only lead you into trouble. The reason is that a sub-item created in the grid will not have the source field checked, but a sibling item, originally created as a top level item but later on moved under a parent will have the source field checked. So you'll end up to two siblings with different field values. Assuming the grid source is Field1:

Item 1
1. Item 1.1
2. Item 1.2

So in the above example, if Item 1.2 was initially created as a TLI, you'll have Item 1 and Item 1.2 with Field1 checked but not Item 1.1.

Finally, when showing screen shots make sure you include the whole IQ Window, so we can know what is the display mode

HTH !

Pierre_Admin

IQ Designer

[quote=Pierre_Admin]

Item 1
1. Item 1.1
2. Item 1.2

So in the above example, if Item 1.2 was initially created as a TLI, you'll have Item 1 and Item 1.2 with Field1 checked but not Item 1.1.

[/quote]

I don't think I said that it was the way to go in general (i.e. that it should be the default for everything).

How and why could that option lead me/us into "trouble", in general (and concretely)? (Apart from the fact that 1.1 and 1.2 don't match.)

IQ geek

Windows 8.1

CPU: Intel i5 2.6ghz

[quote=Armando]

How and why could that option lead me/us into "trouble", in general (and concretely)? (Apart from the fact that 1.1 and 1.2 don't match.)

[/quote]

Well, for one, if the grid display is not set to Normal, you can get unexpected list of items:

Flat list

+ Item 1
Item 1.2

i.e. Item 1.2 is shown but not Item 1.1. Also item 1.2 will appear under Item 1 (when expanded) and in TLI

Tree view

- Item 1
1. Item 1.2

Item 1.1 is nowhere to be seen, unless one uses Item > Show all sub-items

Pierre_Admin

IQ Designer

[quote=Pierre_Admin]

[quote=Armando]

How and why could that option lead me/us into "trouble", in general (and concretely)? (Apart from the fact that 1.1 and 1.2 don't match.)

[/quote]

Well, for one, if the grid display is not set to Normal, you can get unexpected list of items:

Flat list

+ Item 1
Item 1.2

i.e. Item 1.2 is shown but not Item 1.1. Also item 1.2 will appear under Item 1 (when expanded) and in TLI

Tree view

- Item 1
1. Item 1.2

Item 1.1 is nowhere to be seen, unless one uses Item > Show all sub-items

Pierre_Admin

IQ Designer

[/quote]

"Outline (Normal)" (which is the default mode) is supposed to show the full hierarchy, no need to use "show all sub-items". Unless secondary filters are applied (and that's always true, whether subs meet the source or not, or if other viewing modes are used).

So this does not happen to me, and I don't see why it should happen to anybody else.

"Problems" will only arises if one selects "source items (flat list)" or "source items (tree)", as they filter more aggressively.

But I wouldn't call it "problems" anyway, since the behavior is easy to understand : only items meeting the source show up.

In your example, it's the fact that an item shows up and not the other that could be seen as a problem, but it's expected. And if it's not expected, it's probably easier to remove the offending field in item 1.2 to prevent it to show it up than to deal with situations where one forgets an item even exists because it's nowhere to be seen.

EDIT : so, IMO, what's harder to understand is why changing an item's position in the hierarchy should also change its type or some other status. (I.e. demoting a task --> NOT a task anymore)

IQ geek

Windows 8.1

CPU: Intel i5 2.6ghz

This is getting rather off-topic, I wonder if Chris got this cleared up (my post was never answered)

[quote=Armando]

"Outline (Normal)" (which is the default mode) is supposed to show the full hierarchy, no need to use "show all sub-items".

[/quote]

Agreed. Exactly what I said, it is the other 2 display modes that can be an issue

[quote=Armando]

"Problems" will only arises if one selects "source items (flat list)" or "source items (tree)", as they filter more aggressively.

[/quote]

Not really, they just show raw items, treating hierarchy as just an attribute (which it is, really)

[quote=Armando]

IMO, what's harder to understand is why changing an item's position in the hierarchy should also change its type or some other status. (I.e. demoting a task --> NOT a task anymore)

[/quote]

Not quite... dates are never removed, so Todo dates for example will never be deleted when an item is demoted. The same for non-default text and numbers. Yes/no fields will get unchecked unless the grid has the setting to keep source

For the record, Ecco Pro, an award winning PIM, deleted all source field values when demoting, even dates !!

Pierre_Admin

IQ Designer

I think my point is/was pretty simple, but there's obviously a perspective difference that seems difficult to reconcile. No problem.

However, I can assure you it has nothing to do with "hierarchy" being an attribute, dates (and other stuff) not being deleted, ToDos (or even contacts,projects etc.) being defined by dates or some other data type rather than boolean/yes-no fields, and Ecco Pro being an award winning PIM.

I don't have any problem with David bringing up the question of making the "Keep source field values when demoting" option the default option, but since I didn't bring it up myself (and it's not "my" thread), I'll leave it there.

I'm open to discuss the matter further if needed.

Hi Pierre,

Yes I did get it solved. Thanks much for the help in returning my orphans to their rightful home.

I also noticed that you now have a home grid property. Seems as I move forward that will be the answer to my runaway orphans.

Sorry for not responding sooner I've just been swamped with work. It doesn't seem to be letting up.

Thanks for all you are creating with InfoQube.

Cheers,

Chris