Submitted by jan_rifkinson on 2012/04/21 12:27
It seems that all column values that play a part in an equation must be VISIBLE.  I'm trying to reduce the number of columns in a grid. 
 
If user's rate is a consistent, why can't I create a default value that is added AUTOMATICALLY. From Help file I understand dbl click on cell will MANUALLY add default value. 
 
 
04/26/12 bumped
 
 
 
 
 
 
g

Comments

Maybe default value is a "grid feature" (rather than db/source level?).
 
I know equations run regardless of column visibility so you could do it there with either a row equation that "depends" on Item or a push equation in Item that sets the default value.
 
d

jan_rifkinson

2012/05/15 13:57

In reply to by reesd

[quote=reesd]
Maybe default value is a "grid feature" (rather than db/source level?).
 
I know equations run regardless of column visibility so you could do it there with either a row equation that "depends" on Item or a push equation in Item that sets the default value.
 
d
[/quote]
d, Thanks for replying.
 
Maybe I'm looking at this the wrong way but it appears to me that the default value is not added to the grid cell unless some manual action takes place
And until the default value is inserted to the grid cell, the row equation doesn't seem to work. 
Of course there is the genuine possibility that I'm doing something wrong.

Armando

2012/05/16 15:16

In reply to by jan_rifkinson

 
hi Jan,
 
What you'd probably want to explore is a solution similar to what Dave suggested.
 
E.g. : In the source field for the grid where you want w2w_work_rate = 100 by default (don't know what is your source field for that specific grid), add this in the auto-assign rules : A:w2w_work_rate=100.
You might want to add its "opposite" too :  E:w2w_work_rate=""
 
Now, everytime you'll add an item to this grid (TLIs only, unless w2w_work_rate has some inheritance going on), w2w_work_rate will be = to 100.
 
If you want every single item created in that grid to have a w2w_work_rate=100, you should then have that either that field set with inheritance on, or maybe another one you'll create just for that prupose. Be careful with inheritance though as it can quickly get out of control (since any children put under a parent with that field "checked" will inherit it... and the associated behaviors...).
 
--------------------------------------------------------------------------------
Windows XP Home Edition, Service pack 3
Dell Vostro 1500, Ram:3gb, CPU: Intel Core2Duo T7500 2.2ghz

jan_rifkinson

2012/05/16 18:04

In reply to by Armando

Thanks Armando...and Dave.
 
Armando, to answer your question the source field for the grid is w2w. (This field brings up items (contacts) in the contact list that are w2w clients & all their w2w appts)
So none of the equation lines are TLI's 
All appear as children of the contact entry which is the TLI
 
This way whether I look up contact / client in Contact List or in w2w grid, I see all activities listed, whether w2w or not
 
Double clicking the field for automated entry is not a big deal as IQ does the rest of the work. .
 
 
 

Armando

2012/05/16 18:36

In reply to by jan_rifkinson

Everything is fine then !
 
You could still try automating the assignation of 100, by putting these your w2w auto-assign rules :
A:w2w_work_rate=100
E:w2w_work_rate=
 
 
--------------------------------------------------------------------------------
Windows XP Home Edition, Service pack 3
Dell Vostro 1500, Ram:3gb, CPU: Intel Core2Duo T7500 2.2ghz

jan_rifkinson

2012/05/16 19:56

In reply to by Armando

Everything is fine because it works & I don't mind dbl clk to enter the value
 
I was just trying to figure out how to eliminate two columns w default cell values
It appears the row equation only seems to work if all the columns & cells which are part of the equation are visible in the grid. 
 
I did do it but don't see / understand the difference if it is there or not in my case. 
Can you explain what the advantage is. 
In either case, it appears that I have to dbl clk to get the default value inserted in the cell
OTOH, I may be missing something. 
Thanks.

Armando

2012/05/16 21:57

In reply to by jan_rifkinson

Note that I'm not talking about a row equation but an auto-assign rule. The only advantage is that each time you'd create an item with the field w2w (or whatever) you'd have the value added to that other field automatically .
--------------------------------------------------------------------------------
Windows XP Home Edition, Service pack 3
Dell Vostro 1500, Ram:3gb, CPU: Intel Core2Duo T7500 2.2ghz

jan_rifkinson

2012/05/17 11:05

In reply to by Armando

 Armando, from your reply I take the following:
 
(1) adding the equation will produce a value every time I enter 2 w2w item as a top level item
(2) adding the equation might / might not work for a row equation depending on whether the item is a TLI.
 
Do I have this right?

Armando

2012/05/17 15:46

In reply to by jan_rifkinson

>(1) adding the equation will produce a value every time I enter 2 w2w item as a top level item
 
Everytime you'll create a TLI in your w2w grid (unless you add the field to the "auto-assign the following fields" option in  "manage grid", "data" section, in which case this will work for ANY item added to the grid) the w2w w2w_work_rate field will get its "100" value.
 
>(2) adding the equation might / might not work for a row equation depending on whether the item is a TLI.
 
I'm not sure I understand this last one. The rule I suggested has nothing to do with row equations. You could of course rely on a row equation instead but something would have to trigger it -- it could be the item field + some other field but I don't see the advantage.
 
--------------------------------------------------------------------------------
Windows XP Home Edition, Service pack 3
Dell Vostro 1500, Ram:3gb, CPU: Intel Core2Duo T7500 2.2ghz

jan_rifkinson

2012/05/18 09:03

In reply to by Armando

 
oK. Thanks much, Armando. Appreciate the feedback / help. Have a nice day.