Column Chart in Email Document
Leave feedback
NoteIn this article, we will use GroupDocs.Assembly to generate a Column Chart Report with Filtered, Grouped, and Ordered Data in Email Document format.
Please follow below steps to create a column chart in MS Outlook 2013:
- Create a new Email.
- Click the “Insert” tab, and then click “Chart” in the illustrations group to open the “Insert Chart” dialog box.
- Select “Column” in the sidebar, you will see a gallery of charts.
- Select the “100% Stacked Column” and press “OK” to insert the chart and Worksheet template to your email.
- Edit the Worksheet with your data to update the chart.
- Save your Email.
As a report developer, you are required to share orders quantity of the customers dynamically with the following key requirements:
- Report must be in .eml or .msg format.
- It must add email recipient, css and subject of the email.
- Report must show total Contract Prices by Quarters
Total Contract Prices by Quarters<<foreach [in getContracts()
.where(c => c.getDate().getYear() + 1900 == 2015)
.groupBy(c => c.getManager())
.orderBy(g => g.key.getName())]>><<x [key.getName()]>>
| 1st Quarter<<y [where(c => c.getDate().getMonth() >= 0 && c.getDate().getMonth() <= 2).sum(c => c.getPrice())]>> | 2nd Quarter<<y [where(c => c.getDate().getMonth() >= 3 && c.getDate().getMonth() <= 5).sum(c => c.getPrice())]>> | 3rd Quarter<<y [where(c => c.getDate().getMonth() >= 6 && c.getDate().getMonth() <= 8).sum(c => c.getPrice())]>> | 4th Quarter<<y [where(c => c.getDate().getMonth() >= 9 && c.getDate().getMonth() <= 11).sum(c => c.getPrice())]>> |
Category 1 | 4.3 | 2.4 | 2 | 3 |
Category 2 | 2.5 | 4.4 | 2 | 2 |
Category 3 | 3.5 | 1.8 | 3 | 5 |
Category 4 | 4.5 | 2.8 | 5 | 2 |
Please download the sample Chart Template we created in this article:
NoteThe code uses some of the objects defined in: The Business Layer
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.