Business Intelligence in the Cloud: Zoho Reports


I discovered today in the chrome webstore a nifty little business intelligence offering from Zoho.

Zoho Reports

So I uploaded some exports from Salesforce.  First we’ll take a look at the login activity data, which begins to point towards how one audits things in the multidimensional space that is a database in the cloud, towards which lots of web services are making calls.

Salesforce Login Log Export - in Zoho Report (Table)
Salesforce Login Log Export – in Zoho Report (Table)

The summary function reporting of Zoho’s BI Tool is just like a SQL/MS Access GroupOn[Value] query.  It enables us to take this table of 1,691 rows and look at the clustering of values.  To tmake this interesting, I choose to Group On (and thereby collapse around) the LoginType field. And count the records to produce the following distribution histogram:

 Distribution Histogram of Login Type:  Humans aren't even close!

Distribution Histogram of Login Type: Humans aren’t even close!

Absolute Automation is the name of an app by IHance, and it’s an email matching app that takes all email to my address and tries to find a Salesforce record to attach them to — it makes for a very thorough approach to CRM, which is rather exactly what we’d expect from Salesforce.com

Cirrus Insight is an app that syncs Google Apps contact data with Salesforce — and enables creating new accounts & contacts & leads from within the Gmail interface..  Those 175 entries via the browser — that’s me as the admin: a living, breathing mortal who is a mere  piker in comparison to the hard working apps  Such is the beauty and power of Cloud computing

.

Record Type Agreement between Salesforce.ACCOUNT object and Salesforce.CONTACT.

SF.CONTACT fields are shaed in Gray; SF.ACCOUNT fields are in Blue; Dark blue is redaction of Alumni personal data
SF.CONTACT fields are shaed in Gray; SF.ACCOUNT fields are in Blue; Dark blue is redaction of Alumni personal data

Record type agreement — after all my bellyaching about the importance of a record type schema that can handle the complexity of the milieu in which an Ivy League Alum Club operates. Record type agreement is one way to track if one’s practice lives up to one’s theory.   Furthermore, this little exercise is providng an awfully convenient excuse to dig deeper in Zoho Reports.  Pretty nifty the  way it’s  just a few short clicks until you can make some interesting discoveries.

The image below shows a portion of the 1700 plus rows in the table.  The grey shaded portion are SF.CONTACT object fields; the light blue are SF.ACCOUNT object fields.  And the dark blue are redaction on my part to safeguard my alumni data.

When I was enthusing earlier about dataloader.io, this is why:  if you don’t pull over related records’ actual fields, to look at a Salesforce export — well for a human, it’s often not an easy read: long strings of digits in which upper v. lowercase actually counts!

One nice diagnostic test to run is to compare counts of Salesforce CONTACT records, by record type, against the number of organizational ACCOUNT records, by record type.  The logic of the nature of the relatioships that are to be expected helps one to ascertain how well the coding schema is working.  So, again, using GroupOn ACCOUNT.Organization Record type:  what inferences can we make about the SF.CONTACT records by type?

Take a look at the entires in the report and, as Linda Richmond would say: “discuss amongst yourselves.”

I’ll use non-Linda-Richmond diction by noting that I’ll return to this anon.

red needs further investigation green is exactly or almost exactly as one would expect yellow is pretty good oh, provided you’re using a non-free account, it’s basically one-click publishing of your data. Take that, SharePoint 2013!
red needs further investigation
green is exactly or almost exactly as one would expect
yellow is pretty good
oh, provided you’re using a non-free account, it’s basically one-click publishing of your data. Take that, SharePoint 2013!

 

More Walking that Walk: Salesforce.com Coding Schema for an Cloud-Based Alum Club


So, I had been regaling you the way the person, me:

Darren Scott Kowitt, a new yorker by birth but a washingtonian by circumstance  got to new york first by way of new haven (isn’t that coy!) and in new york I studied marketing at Columbia Business School before coming to DC for love

Now Salesforce.com is  a robust platform.  It likely could accomodate stories like that without too much difficult int the hands of the appropriate database & platform administrator.  but all that broadband personhood i suggestively sketched above — well, it has to be shoe-horned into an unmovable and unforgiving fact about Salesforce.com.

it’s staring you in the face with the name: it’s got sales in its DNA. and sales means nothing without [ACCOUNTS]..  Where there are [ACCOUNTS] there may be people.  so in terms of the Salesforce.com instance for Columbia Business School Alumni of MetroDC , this is how it plays out concretely:

I, Darren Kowitt, who graduated from Columbia in 1997, I Darren am represented in the database when first loaded/created as:

[ACCOUNT]=MBA’97: Kowitt, Darren

[ACCOUNT].[CONTACT] = Mr. Darren S. Kowitt, residing at…born on…

with as much detail as External Relations in New York cared to provide me with

note how the [ACCOUNT] record is functioning/quacking like an Alum Household — to which a subsidiary partner or spouse might be easily attached — and, provided the coding schema is rigorously applied, and attached in such a way as to be acknowledged and included where appropriate — but not gratuitously and carelessly.  this is not an accident.  It’s important to remember that coding is a choice of how to represent reality (in all its potential complexity) in the database.

running an ivy league alumni club in a major metro is stimulating and at its best, fun.  but it takes a lot of partnering.  the people i deal with, wheedling, cajoling, begging, borrowing — oh and let’s not forget: drinking with, conversing expansively with, but also receiving upon their arrival at Union Station,. these personages, some august, others less so — well there’s no easy way to categorize them all: so here’s an attempt at conveying to you the breadth of their diversity:

  • Alumni (they’re easy: that MBA’YY: LName, FName sees to that)
  • Spouses do show up, but not as often as you might think
  • Professors visit from new york
  • Admissions stages its dog & pony show each fall
  • Applicants paw at us, rending our garments in their over-eager enthusiasm to simply put their nose up against the iorn fence. But I digress
  • the Columbia Business School Alumni Board of course has much traffic with the board of the Columbia University Club of Washington, DC (and in truth, my alums are truly, fully Columbian in both senses)
  • but we don’t always keep in the family: sometimes we even collaborate on programming with those people from Cambridge, Philadelphia, Chicago, and Palo Alto (the dirty secret of competitive MBA populations is: in the long run, excellence converges)
  • i’d be remiss in not mentioning congress members, their staff – and the economics/policy beat journalists  we run with
  • Compass Strategic Guidance. Stronger Non-Profits,
  • and then there is a wonderful organization called CompassDC whose purpose is to harness all that pan-ivy-league intellectual firepower towards helping regional non-profits change for the better and indeed even thrive.  every fall they recruit pro bono volunteers for a 7 month collaborative consulting project.

Some of the relationships are essentially/practically permanent:  for better or worse, I shall remain myself until I die.  thus MBA’97: Kowitt, Darren is quite strongly tied to Mr. Darren S. Kowitt.  not all relationships are quite so durable, however.  and this is not merely truth spoken from a broken heart.  an Alum Club Board has terms of office — or at least in theory good governance principles somehow suggest that, even if  such evasions of the unspoken still amount to quite the opposite of permanence,  and those Compass projects are by their nature fixed in term.

So the data I want to capture in my CRM system is, to be polite, heterogeneous.  And thus every time I set about creating a new Alum in the database, am I faced with this  choice

Ar the moment of creation: what a choice!
Ar the moment of creation: what a choice!

–somewhat paralyzing to the unititiated, I’m afraid.   and i’ll leave you to mull over that for now.