InfoQube IM - Community

Submitted by jan_rifkinson on 2009/10/06 12:28

Situation:

Contact list = boolean field

Properties: inheritance value -> sub-items is un-checked

Equations: hierarchy equation is none & blank

any item entered within Contact list grid is automatically assigned to 'contact list' field

so far so good

To get phone #, etc I find contact & create a sub-item within contact list grid

the child (sub-item) is also automatically assigned to 'contact list' field

Is this right?

I do want to be able to call up a contact & get the history of my interaction with them.

If this thread is in the wrong place, move it where it should be .... discussion perhaps

To me, it seemed like a bug but I'm never sure

Thanks.

Comments

> [...] I find contact & create a sub-item within contact list grid

> the child (sub-item) is also automatically assigned to 'contact list' field

that shouldnt happen (well doesnt happen here...)

I presume the source is 'Contact list' (just in case:- is there a space in the field name ? - I thought spaces didnt work ?)

I'm not sure how that relates to this:

> I do want to be able to call up a contact & get the history of my interaction with them.

Are you not able to do that?

[quote]

that shouldnt happen (well doesnt happen here...)

I presume the source is 'Contact list' (just in case:- is there a space in the field name ? - I thought spaces didnt work ?)[/quote]

source = all items

filter = Contact List

Jan Rifkinson

Ridgefield CT USA

HP Blackbird Vista Ultimate SP-2

Perhaps Grid>>Properties>>Date>>"Auto assign the following fields" is not blank...

That must be it.

And just in case : Grid>>Properties>>Data>>"Auto assign the following fields"

;)

Thanks Pierre, Not blank. Has 'contact list'.

Question: if I enter a name in contact list I will then have to assign it manually if I remove this. Is that right?

Jan Rifkinson

Ridgefield CT USA

HP Blackbird Vista Ultimate SP-2

> Question: if I enter a name in contact list I will then have to assign it manually if I remove this. Is that right?

In my database (it may depend on settings) it works like this:

with Contact List as the source
if the name/new item is entered as a top level item it will automatically have the source field applied to it
if that item is moved down the hierarchy it automatically loses the Contact List field
if a sub-item is moved up the hierarchy to top level it automatically regains the Contact List field

Someone else will have to say if this is always the case or not

yes... unless, as tom esplained, it's a TLI. Tom has it right -- this works only for simple sources (one field in the source box), and then there are a few other cases when sources are complex... see Grid Source EditBox

[quote]

1- when the logical AND operator is used between the first fields (any number of them) in the expression, these fields will be treated somewhat similarly as a simple source and all will be added to TLIs (eg : grid1 AND grid2 AND grid3 AND grid4 OR grid5 ---> the grid1, grid2, grid3, grid4 fields will be assigned to TLIs)

2- in an expression combining AND and OR, any field added after an OR operator won't be assigned to TLIs

3- when the logical OR operator is used between fields, only the first one of the expression will be assigned to TLIs

4- For the More complex expressions using not only OR and AND, but also other operators and comparators (Like, is not, ...) (eg : (Grid1 AND test IS NULL) AND itemcreated IS NOT null), no specific fields at all will be assigned to TLIs -- if the user wants to have some field automatically assigned to a grid, one needs to be explicit about them in the "manage grids" dialog.

[/quote]

Anyway, in the case of simple sources, the logic behind what Tom described is that TLIs are the "main items" (the contats, in your case), and the sub items might not be contacts (but maybe phone calls, meetings, invoices, reminders, etc.).

Thanks Pierre, Tom & Armando for explaining this to me. One would think after all this time using IQ, I would have known but noooooooooooo, not me. Sometimes I think I have to go back to square one. OTOH IQ does a lot of things for me on a daily basis so something must be working in my grey matter.

Jan Rifkinson

Ridgefield CT USA

HP Blackbird Vista Ultimate SP-2

Be kind to yourself! I think it's normal that you don't know that... because it's not a transparent behavior.

I've discussed this issue with Pierre and I think he's planing to make more explicit which fields are automatically assigned to items depending on the grid source (e.g. : by having these fields appearing automatically in the auto-assign section of grid management dialog).

(He'd have to confirm that though...)

[Edit : Speaking of that, maybe there should be 2 different "autoassign" in the grid : 1- autoassign to TLIs only, 2- and auto assign to all items.]

===================

Another issue which hasn't been completely resolved is to make more transparent the reverse aspect : removal of field values when moving items around (TLI-->sub-item, Item from grid1 to grid2, etc.). see Discussion about IQ's treatment of item field(s) auto-assignation in relation to the grids' sources and Grid Source EditBox

The fact that grids are described as display "devices" for items is also a tad misleading in that effect since they don't just do that : they can also assign values to items. This, I think, is a bit of a problem in terms of coherence -- but certainly not an unsolvable one if the process of assigning and de-assigning field values can be made more explicit, transparent (through the grid management window, and mouse hovering over grid tabs could make a grid info popup -- this used to work, but hasn't in a long while...)

[quote] Be kind to yourself! I think it's normal that you don't know that... because it's not a transparent behavior. [/quote]

Perhaps, Armando, but it appears we agree more has to be done to clarify functions, etc. Sometimes I think we miss the trees for the forest. Specifically, if that property was described as "auto assign to TLI & children" I might have had a chance of understanding it.

Too much is taken for granted in this program. The help files are very specific about explaining or solving a problem but fail to tell the user how to get to that point in the resolution or explanation, i.e. the basic steps -- Ex: Main Menu > View > Grid> Grid management > select grid in question > properties

IQ is so pliable, complex, dependent on so many functions working in concert, that I think we have to take extra steps to make everything super clear. Most people don't have the kind of time a few of us spend on this program, asking questions, debugging, testing, etc.

Jan Rifkinson

Ridgefield CT USA

HP Blackbird Vista Ultimate SP-2

Jan,

at this stage I'm chuffed if I know more than you

lol

Tom :-)

Tom: you'll have to define "chuffed" for me to fully appreciate your comment.

Jan Rifkinson

Ridgefield CT USA

HP Blackbird Vista Ultimate SP-2

[quote=jan_rifkinson]Tom: you'll have to define "chuffed" for me to fully appreciate your comment.

[/quote]

I guess that is a particularly English expression - I wouldnt even use it that much myself (I'm Irish)

via the thefreedictionary.com:-

chuffed

Adjective

Informal pleased or delighted: I suppose you're feeling pretty chuffed [origin unknown]

ThesaurusLegend: Synonyms Related Words Antonyms

Adj.

chuffed - very pleased; "I'm chuffed to have won"

child assigned to boolean field w/o inheritance option

Comments