Hi,
I’ve got a view that i would like to show icons for values.
Column 1 is the user the call has been assigned to. Column 2 is a total column and column 3 I would like to show a green tick if the number of calls is below 3 and a red cross if its above this value.
Anyone got any pointers? I have been playing about with the property ‘display values as icons’, but dont really know what i’m doing.
Thanks
F1H
Subject: View Icons
F1H,
Check the Domino Designer help under the section Displaying Icon Values in a Column. That shows how to go about populating the column with icons. Probably what you need is to create an @If statement that resolves to the text name of the image resource once you have entered it, kind of like this:
@If(Calls < 3;“greentick.gif”;Calls >= 3;“redcross.gif”;“”)
Of course I have never tried to do this, but it seems logical to me.
hth.
brandt
Subject: RE: View Icons
when using filenames → “redcross.gif” must be a image resource in the database.
Subject: View Icons
Mark the column “Display values as icons” and use this formula @If(Calls < 3;82; Calls >= 3;81 ;“”)
Note that the values must be numeric.
See also "Displaying an icon in a column " in Designer help
Subject: Ok…but…
The problem is that there is no field called “Calls”, i would like to base it on how many are listed under that name.
so its based on the amount of documents in the view, not a field value.
is this possible>?
Thanks
F1H
Subject: RE: Ok…but…
F1H
Why not pick a field on the document and then do an @DBLookup to grab all docs with the person’s name you are looking for and setting the resulting text list equal to a temp variable? then do an @Elements on the temp var to find out the number of elements. Then do the check I specified by using the field Calls, which was just a generic way of specifying how you would need to format your @If statement. Calls could be a temp variable like so
calls := @Elements(listVar)
where listVar is the temp variable you set your @DBLookup results to.
make sense?
brandt
Subject: RE: Ok…but…
brandt,
Good point… how about this for the formula to the column:
listvar := @DbLookup(“”;“”;“(CallLU)”;SysAssTo;2);
calls := @Elements(listvar);
calls
Not doing anything with icons yet…want to make sure its working…which unfortunately, it isn’t yet!
Any ideas as to where i have gone wrong?
Thanks for your help.
F1H
Subject: @DBlookup can’t be used in a column calculation, following taken from help for @dblookup
“UsageThis function does not work in column or selection formulas, or in mail agents.”
Subject: RE: @DBlookup can’t be used in a column calculation, following taken from help for @dblookup
Thats pants!..I was so close too!!
Thanks for pointing that out.
Anyone got any other ideas?
Thanks
F1H
Subject: RE: @DBlookup can’t be used in a column calculation, following taken from help for @dblookup
It can, however, be used in a field on a profile doc and the resultant value CAN be used in the Column formula…
brandt
Subject: RE: @DBlookup can’t be used in a column calculation, following taken from help for @dblookup
How’s that? Profile docs aren’t displayed in views, you can’t use getprofilefield formula in view columns, so I don’t see how they can be displayed. Would be useful to know how.
And of course profile documents are cached so any changes to number of docs won’t be displayed until the application is closed and re-opend.
Dan
Subject: RE: Ok…but…
You can’t use @dblookup in a view column. A view column can only present data in the document itself.
I think the suggestion was to store the related number of docs in each document. THis could lead to lots of problems with updating of course depending on the size and usage of your database.
Basically what you’re trying to do is not really what views are designed for (if this was a web view there are ways round it I guess, but in Notes there aren’t really).
You could look at creating a report doc on the fly. I guess if the numbers aren’t too high this would be fairly quick to do, although would obviously involve coding up a pre-defined doc which could show a green tick or red cross depending on the value of a field. Each line of the view would be stored in different multi-value fields nicely lined up (or you could create a rich text table to store the values)
hth
Dan
Subject: RE: Ok…but…
Thanks Dan,
I will look into this in more detail.
Thanks for all posts on this matter
F1H