Currently it looks like it works with or w/o braces & I have utilized both styles but I'd like to standardize them. 

Therein lies my problem(S).

 

I can change the wikitag field w/o a problem; it adds to the drop down list

But I don't know which way to go, i.e.

 See attachment

How do I create a template that looks like this:

 

 

and get it to load up automatically.  I got this by clicking about haphazardly and got exactly what I wanted, but I don't know what I did.

 

TIA for your help.

 

Hi,

Would anybody know why Advanced Find is suddenly returning all 8,144 Items in my IQ database instead of the searched-for item?  It was working fine one or two days ago, but bresumably a setting somewhere has changed, but I wouldn't have a clue what, where or how?

thanks to anybody who can help

Doug Bartlett

Would it be possible to have a 'Clear' button on the tagged items heading in the properties pane?

 

I know you can right click the area with the tagged items and select clear list, but it seems to be an operation that is used enough to maybe make a button worthwhile.

Hi all. I'm curious if there's a way, or any additional interest apart from mine in a way, to qualify a field so that it is upwardly inheritable. My particular wish is to have it that when a box is checked for a given item, that that checking would be reflected in the item's parents and grandparents as well. That way I can browse on a higher level and know that a given parent has at least one child with a given attribute. Doable or maybe not worth it?

 

~Thom

1- in a grid, I focus on an item which has a multiple parents, not present in the grid.

2- I click on the parent name in the "parents" section of the properties pane,

2- the scratch pane opens as it should but there's (often) a display problem.

 

It happens about 70% of the time.

 

Here's what I see :

 

Using the parent <-> child relationship to create links between items has a lot of advantages :

 

1- you can directly see the items when they're linked (below the parent, or using the context parent, or just looking at the properties pane)

2- all parents or children are visible in the properties pane,

3- you can transfer data from one item to the other through inheritance or column equations,

etc.

 

However, some of these strengths are also weaknesses. One of them : if an item has multiple parents, which themselves are children of multiple parents, etc. column equations can rapidly spiral out of control and IQ's performance decreases dramatically. This is a big problem in my DB now. Sometimes an operation on 1 item takes 15s !

I meant to say it for at least 2 weeks... So, here !

Did you guys notice ? Now the column filter buttons, when ON (Grid menu -> column filter -> click on "Column filter button"), auto hide when the mouse is over the column header. Very convenient. I can now have my narrow columns AND also the button when I need it. Better then having to right click and then choose the right option in the context menu.

Pierre, this needs to be explained or fixed (together with the other inheritance problem). My DB is presently a bit of a mess and I'd like to "clean" it.

 

In a sample DB :

 

1- go to the project grid

2- Drag the project field in the grid from the properties pane  so that it's visible.

3- in the second visible item ( "Design" ), Write "Hello" in project field

4- Now go to the TLI and, again in the project field, change "Somiro" for "Somiro Test"

5- The second item's "Hello" stays... "Hello", all others are changed.