Lookup doesn't quite work with many sub categories yeah?

i spent one day to study this problem, I tried made a lookup , which will get the total of all the documents having the same key code.

However, I noticed that if I have many subcategories under this key, it will only pickup total values of the first sub category.

Am I right? Is this how it should work?

So, I delete the other columns, it will just sum up all the values under that key (which is a categorised column).

I used @sum(lookup), where lookup refers to @Lookup formula, a variable that I hv declared earlier.

tq.

Subject: Lookup doesn’t quite work with many sub categories yeah?

You could try creating a special view with a single column that is sorted but not categorised.

Depends how you are subcategorising but assuming its different fields, create a column whose value is

Value1 + “|” + Value2 + “|” + Value3…

Then you can do a simple dblookup of one column.

Multiple key lookups can be iffy, for example they dont always work if one of the values is numeric. Use strings always, and if possible, concatenate to a single unique key.

Simon

Subject: Lookup doesn’t quite work with many sub categories yeah?

There are issues with multiply categorized views being used in @DbLookup formulas. But there is no reason you cannot make the view columns merely sorted, and not categorized, right? If it’s a view people use, then make a copy which is hidden and used by your lookup formulas.

See articles on performance and views in DeveloperNetwork for a bit more info on this topic.

regards,

raphael