Bubble Chart in Email Document Leave feedback
NoteIn this article, we will use GroupDocs.Assembly to generate a Bubble Chart report in Email Document.
NoteThe example reads the shop data described in The Business Layer.
As a report developer, you are required to share your sales/orders dynamically with the following key requirements:
- A report must be in .eml or .msg format.
- It must add email recipient, CSS and subject of the email.
- Retrieve total order Prices by Months.
Orders Prices by Months<<foreach [in orders
.GroupBy(c => c.OrderDate.Month)]>><<x[Key]>>
X-Values | Total Order Price<<y [sum(c => c.Price)]>><<size[Count()]>> | Size |
0.7 | 2.7 | 10 |
1.8 | 3.2 | 4 |
2.6 | 0.8 | 8 |
TipFor detailed technical information about syntax, expressions and report generation by the engine, please visit: Working with GroupDocs.Assembly Engine.
Please download the sample Bubble Chart document we used in this article:
import json
from datetime import datetime
from groupdocs.assembly import DataSourceInfo, DocumentAssembler
def parse_dates(item):
# JSON has no dates: turn the order dates into datetime objects for the template
for key in ("OrderDate", "ShippingDate"):
if key in item:
item[key] = datetime.strptime(item[key], "%Y-%m-%dT%H:%M:%S")
return item
with open("orders.json", encoding="utf-8") as f:
orders = json.load(f, object_hook=parse_dates)
assembler = DocumentAssembler()
assembler.assemble_document("bubble-chart.msg", "bubble-chart-report.msg", [
DataSourceInfo(orders, "orders"),
DataSourceInfo("Harbor Lane Provisions <orders@harborlane.example>", "sender"),
DataSourceInfo(["Quayside Bistro <orders@quaysidebistro.example>", "jonas.weber@harborlane.example"], "recipients"),
DataSourceInfo("amara.osei@harborlane.example", "cc"),
DataSourceInfo("Bubble chart", "subject"),
])
The following sample file is used in this example: bubble-chart.msg
The following sample file is used in this example: orders.json
Binary file (MSG, 63 KB)
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.
