Customising Analytics

The Analytics module provides you with the ability to easily retrieve statistics for your business in a printable view. Analytics consist of Dashboards and Reports.

Dashboards

Dashboards are graphs, displaying key information and statistics. Within CRM.COM Software, you have the ability to create new or edit existing dashboards, adding the required content and layout, extracting useful information about your business without the need of programming skills. Dashboard is a visual summary of data which provides statistics based on information fusion from multiple records of a given entity, based on criteria set by the user. Each user can create a new dashboard based on his/ her needs and requirements. A dashboard can be set as private through CRM.COM Software, so that it will only be visible by the owner, but it can also be set as public to all or to selected group of users.

Reports

CRM.COM Software offers you the ability to create Custom Reports for you, and then upload them in the system through an Integrated Upload Utility. Custom Reports are created according to your business requirements, have the format you need and display the results in the way you require. The uploaded reports will be available for the users of the Software in the special location for Custom Reports. In order to create custom reports, you must be aware of and use the iReport tool and definitely have experience with Java (Object Oriented Programming Language) and SQL (Structured Query Language). Assuming that you are aware of the previous requirements, you can construct your own Custom Report. After creating the custom report (crxml file only or crxml&jrxml files), this can be uploaded to the application and set ready for use, downloaded from the system to be modified and/or deleted.

Creating And Uploading A Report

.crxml

<config>
	<name>PaymentsByUser</name>
	<description>Payments By Users</description>
	<defaultgroupby></defaultgroupby>
	<dataset></dataset>
	<sqlansi>
	SELECT p.PAYMENTID, 
	       p.PAYMENTNUM, 
	       p.PAYMENTAMT, 
	       p.PAYMENTCREATEDBYUSERID, 
	       p.PAYMENTCREATEDDATE, 
	       p.PAYMENTAMT, 
	       users.USERNAME, 
	       pm.PAYMETHODNAME,
	       v.VOUCHERNUM, 
	       v.VOUCHEREXPIRATIONDATE,
	       s.SUBNUM
	FROM PAYMENTS p
	INNER JOIN USERS ON USERS.USERID = p.PAYMENTCREATEDBYUSERID AND USERS.USERDELETED = 0
	INNER JOIN PAYMENTMETHODS pm ON pm.PAYMETHODID = p.PAYMETHODID AND pm.PAYMETHODDELETED = 0
	INNER JOIN VOUCHERS v on v.VOUCHERID = p.VOUCHERID AND v.VOUCHERDELETED = 0
	INNER JOIN ACCOUNTSRECEIVABLE acr on acr.ACCRECID = p.ACCRECID AND acr.ACCRECDELETED = 0
	INNER JOIN SUBSCRIPTIONS s on s.ACCRECID = acr.ACCRECID AND s.SUBDELETED = 0
	ORDER BY p.PAYMENTCREATEDDATE,
		 users.USERNAME,
		 p.PAYMENTCREATEDBYUSERID, 
		 p.PAYMETHODID
	</sqlansi>
	<copysqltosubreports>true</copysqltosubreports>
	<hql></hql>
	<criterialist>
		<criteria>
			<ordernum>1</ordernum>
			<criteriatype>0</criteriatype>
			<label>User Name</label>
			<entitytablename>users</entitytablename>
			<entityfieldname>USERNAME</entityfieldname>
			<fieldtype>ftXString</fieldtype>
			<fieldsize>32</fieldsize>
			<displaytable>USERS</displaytable>
			<displaylabel>Person Name</displaylabel>
			<displayfield>UserPersonName</displayfield>
			<sourcealias>UserName</sourcealias>
			<displayalias>UserPersonName</displayalias>
			<datasetname>users.load</datasetname>
		</criteria>
		<criteria>
			<ordernum>2</ordernum>
			<criteriatype>0</criteriatype>
			<label>Creation Date</label>
			<entitytablename>p</entitytablename>
			<entityfieldname>PAYMENTCREATEDDATE</entityfieldname>
			<fieldtype>ftXdatetime</fieldtype>
			<fieldsize>32</fieldsize>
		</criteria>
		<criteria>
			<ordernum>3</ordernum>
			<criteriatype>0</criteriatype>
			<label>Payment Method</label>
			<extralabel>Payment Method</extralabel>
			<tooltip></tooltip>
			<hibernatefield></hibernatefield>
			<entitytablename>p</entitytablename>
			<entityfieldname>paymethodid</entityfieldname>
			<displaytable>Payments</displaytable>
			<displaylabel></displaylabel>
			<displayfield>paymethodname</displayfield>
			<fieldtype>ftXString</fieldtype>
			<fieldsize>32</fieldsize>
			<sourcealias>paymethodid</sourcealias>
			<displayalias>paymethodname</displayalias>
			<datasetname>financialtransactions.loadpaymentmethods</datasetname>
			<treename></treename>
			<multiselect>1</multiselect>
		</criteria>
	</criterialist>
</config>