AIArcsen implements Tableau and CRM Analytics, plus Tableau Next, for organizations in the Gulf and Egypt, on Salesforce, Data 360 and ERP data whose definitions finance has signed off. Leaders act on a dashboard only when its numbers match the ones finance reports, so we settle the definitions and fix the data before the first chart.
What we build
Built from the metric down, so the numbers agree.
Data 360 as the shared layer
Tableau Next uses Data 360 as its data layer, and Tableau Cloud and Server can connect to the same Tableau Semantics models. Both then read one governed set of data, so a figure in Slack matches the one in the board pack.
Metrics defined once
We write each metric with finance and its business owner, then encode it once in the semantic model or the CRM Analytics dataset, so revenue, pipeline and collections mean the same in every dashboard and in every answer an agent gives.
ERP data that reconciles
Tableau connects to SAP HANA, SAP NetWeaver Business Warehouse and Oracle Database. For Oracle Fusion and other cloud ERPs, we land the data in a warehouse or Data 360 first, and check totals against the ERP before anyone sees a chart.
Access by role
CRM Analytics can inherit Salesforce sharing or apply security predicates. Tableau uses user filters or data policies on virtual connections. We test each role, from branch manager to group CFO, so people see only their region, brand or unit.
Numbers where people work
Tableau Pulse sends metric digests to Slack and email, and CRM Analytics dashboards sit on Salesforce record pages. We agree with each team the few metrics it follows, so numbers arrive in tools people already open.
Clean data at the source
Duplicates, blank fields and inconsistent codes are fixed in the source system where possible, then held in place with Salesforce validation and duplicate rules, so nobody corrects a dashboard by hand before a management meeting.
Client work
Data work that analytics depends on, by name.
How we deliver
Questions first, charts last.
Agree the questions
We start with the decisions each audience makes, the questions behind them and the metric definitions finance will sign. That list picks the tool, the data sources and the first dashboards.
Fix and model the data
We profile each source, fix problems where they start, and build the model in Data 360, a warehouse or CRM Analytics datasets, reconciled to ERP totals before anything is released.
Build with the users
Dashboards are built in short cycles with the people who will use them, in Arabic and English where needed, and tested against each role’s access rules before release.
Adopt and hand over
We train creators and viewers, set up Pulse metrics or record-page dashboards, and hand over the model, the metric definitions and a runbook. Our managed services team can run it after that.
Questions we get
Asked by every buyer, answered straight.
Tableau, CRM Analytics or Tableau Next: which do we need?
CRM Analytics, if your users live in Salesforce and want numbers on the record. Tableau Cloud or Server, if analysts blend Salesforce with SAP, Oracle and other sources. Tableau Next, if you want agentic analytics with Data 360 as the data layer. Tableau Next is sold alone or with Tableau Cloud in the Tableau+ bundle.
What happened to Tableau CRM?
It is now called CRM Analytics, and it was Einstein Analytics before that. CRM Analytics is still sold, in Growth and Plus editions, and some Salesforce editions include it. Existing dashboards, datasets and recipes keep working under the new name. We review which ones people still use before building anything new.
Will dashboards work in Arabic?
Dashboard content can be fully bilingual. Arabic is not an interface language in Tableau, CRM Analytics or Tableau Next, so menus stay in English or another supported language. We hold Arabic and English labels in the data, show each user their language, and test Arabic text beside numbers and dates in every chart.
How are Tableau licences counted?
Tableau Cloud and Tableau Server are sold by role: Creator, Explorer or Viewer, and every deployment needs at least one Creator. Tableau Next uses Creator and Consumer licences. Before you buy, we map who builds, who explores and who only reads, because that mix sets the licence count.
Check the data behind the dashboards, before anyone presents them.
Start with a free Salesforce health check
Or talk to the team. See also: Real estate clients · Selected client work.