Agent skill · data analytics · aradotso
power-bi-salespulse-360-dashboard
Master the SalesPulse 360 Power BI retail analytics dashboard for profit analysis, regional insights, and predictive sales forecasting
Why this skill is useful
Provides specific DAX measures and Power Query M transformations that enhance Power BI analytics capabilities.
What it needs
Requires power bi installed locally. About 9k tokens when loaded. Last updated 2026-08-05. 5 stars on the source repository.
What this skill does
Power BI SalesPulse 360 Dashboard Skill Skill by ara.so — Data Skills collection. Overview SalesPulse 360 is a comprehensive Power BI dashboard for retail analytics, designed to transform the Global Superstore dataset into actionable business intelligence. This dashboard provides: Multi-dimensional sales analysis across regions, categories, and time periods Profit architecture mapping with heatmaps and margin analysis Predictive forecasting for 12-month sales and profit trends Real-time alerts for profit margin drops and anomaly detection Multilingual support with automatic localization Responsive design for cross-device viewing The project is built entirely in Power BI Desktop using DAX (Data Analysis Expressions) and Power Query M for data transformation. Installation & Setup Prerequisites Power BI Desktop version 2.120 or higher (download here) Global Superstore dataset (included in repository as CSV) Minimum 8GB RAM for smooth performance Initial Setup 1. Clone the repository: 2. Extract the dataset: 3. Open the dashboard: Launch Power BI Desktop Open SalesPulse360.pbix Wait for initial data transformation (2-3 minutes) 4. Verify data connection: Navigate to Home > Transform Data Check that all queries are loading successfully Close the Power Query Editor Project Structure Core Components 1. Data Model Architecture The dashboard uses a star schema with the following structure: Fact Table: Sales (Orders, Sales Amount, Profit, Discount, Quantity, Shipping Cost) Dimension Tables: Calendar (Date, Year, Quarter, Month, Week) Geography (Region, Country, State, City, Postal Code) Product (Category, Sub-Category, Product Name) Customer (Customer ID, Segment) Relationships: Sales[Order Date] → Calendar[Date] (Many-to-One) Sales[Postal Code] → Geography[Postal Code] (Many-to-One) Sales[Product ID] → Product[Product ID] (Many-to-One) Sales[Customer ID] → Customer[Customer ID] (Many-to-One) 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aradotso/power-bi-salespulse-360-dashboard