Nagalakshmi a reader of Siebel Unleashed blog shared a useful tip yesterday related to configuration of Totals in List Applets
Requirement:
The requirement is to display the totals of certain numeric columns in a list applet under the respective columns. I did not know how to configure this. The ‘Edit Web Layout’ section did not reveal any extra column to display the column total.
The Solution:
There are two properties (flags) for a list applet that need to be set to ‘True’ at the ‘List’ object level
- Total Required
- Total Displayed
Then there is another property called ‘Total Required’ at the List Column Level which needs to be set to ‘Y’ for all those columns for which a total has to be displayed at the end of all the records in the applet.
The totals will then appear in the list applet in the UI. If you would like to remove the total being displayed in the applet, uncheck the ‘Total Required’ property of that list column at the applet level.
My thoughts:
Use caution while using this property. I have seen too many performance issues because this property was set to true for certain columns but a nice tip for beginner.
(5 votes, average: 4.8 out of 5)
Loading ...
5 Comments at "Showing Totals in List Applet"
I agree that the total required functionality is great but as neel correctly ponits out it can be a performance intensive functionality, i have seen it run 3 queries to display an applet when the usual is to run only one time to display the applet.
but there are times when the function is so worthwhile that it should be used.
Hi Neel,
This is Siva daily i have to follow up U’R comments. i am suffering one issue from last 3 days. My workflow is working fine in DEV and Test Environment but not working in Production. i checked This workflow is not active in Production Env but it was activated in production. I increased Log level. i have using these steps in my workflow START step and Business Service and END step. Can please let me know farther where i have to check.
The below two Promo’s are in our Production system and they should have a promoted product attached to it. See the first image below.
You can find this in Production under the promotions list of Canada. If you click on the promo, in the bottom applet click on the promoted products tab, there is a product attached with a price and Incremental quantity. We have a workflow named “CAC SKU Promo Volume Refresh” which should process the below two promo’s and load the LE Incremental field of each promo. The LE Incremental is calculated from these fields.
The issue is that these two promo’s are not getting picked up and/or processed by the workflow. The tricky part is that when I create a promo in test that is exactly as the promo (1-4JR1IR) below, the same workflow is picking it up and processing it as it should. The example promo id in test is ‘1-3VTJCV’.
In a nutshell, for the same promo, the workflow is processing it in TEST environment but not in Production. This is making me believe that something might be different in both the environments in terms of the Workflow, BS the workflow is using and the BC that the BS is calling up on. I tried looking at the BS and everything looks Ok. I want you to look at this workflow, BS and the BC’s to see what is different and specifically towards the logic for picking the records and processing of them. The name of the BS is same as the WF that is given above.
I have to attach screen shotes with U’R gmail…
The first image below is from Production where the WF is NOT Picking it up and/or processing it properly.
The below snapshot is from TEST where the WF processed the Promo as it should.
Hi,
I am not sure this thing can solve your problem exactly or not but there is a way to hit this without affecting performance
Create a Calculated Field with Calculated Value = Sum ([Field1]) + Sum ([Field2])
Piyush,
I dont think your calculated field will work as the calculated field will refer to only one record in BC. But as per Nagalakshmi’s tip it returns the sum of all records. Anyway performance is also not considered when you have a strong requirement from client.
Sekhar,
My calculated field will work for one record at a time. My concent was not to modify the client requirment I was just talking about a way to achieve sum of fields.
Comment Now!