doing the impossible with Diver UNLEASHING SPECTRE Dan Jablonski Senior Consultant Dimensional Insight, Inc Connect:

Transcription

1 doing the impossible with Diver UNLEASHING SPECTRE Dan Jablonski Senior Consultant Dimensional Insight, Inc Connect:

2 SYLLABUS Spectre The Block 3 Project Convert Model to Spectre cbase Build cbase from data Use cbase with existing content Place Spectre content in DivePort Prepare for DiveTab

3 THE GOAL Set up sales data to support ProDiver, DivePort, and DiveTab users using Spectre DivePlans and Markers for ProDiver and DivePort cplans for DiveTab cbase to support everything

4 WHILE YOU WERE AT LUNCH Before lunch, you created Models and a DivePlan New Project expands on that Diveplan No Spectre content yet

5 STEP 1: SET UP THE NEW PROJECT Start Workbench Connect to your server Create a new project Browse to /di/projects/block3 Done! Let s look around

6 SOME NEW LINGO Spectre vs spectre Spectre Content vs Model Content Spectre Build: create a cbase with a.build file or an integrator cbase output

7 SPECTRE BUILD FROM INTEGRATOR Sales_0.int: Same as before; more fields set up Dimensions Info fields Summaries Column Properties

8 STEP 2: CONVERT SALES_0 TO CBASE Open sales_0.int in workbench (with VI) Save As /programs/sales_spectre.int Right-click on the output object Select convert to cbase output Change the output path Run! Dive!

9 NOT QUITE THE SAME AS A MODEL A cbase has less done up front No dimensions, infos, or summaries Set string, date, or numeric type No consolidated multimodels

10 STEP 3: BUILD EVERYTHING AT ONCE Open sales_cbase.int in workbench (with VI) Select the cbase output object Change the output to sales.cbase Select the text input object Change the input to use a wildcard Run!

11 <ERROR> Spectre cbases are just collections of data Less structure than a model Less forgiving of bad data than a model Non-numeric values in columns used as summaries are stored as <ERROR>. 1+1+<ERROR> = <ERROR>

12 STEP 3B: SIDE NOTE ON FILE NAMES Something weird happened during that build Look at the input files: sales_0, sales_1, sales_2, sales_team Fix the wildcard: sales_?.txt Fix the filenames: sales-team.txt use - between words Use _ before the suffix.

13 STEP 4: BUILD FROM SCRATCH Right-click one of the input files (sales_1.txt) Select Generate Spectre Build Script Rename it sales.build Move it to /programs Double-click it to bring up the editor Change the input to sales_?.txt Change the output to /cbases/sales_build.cbase Save! Run! Dive!

14 STEP 4: BUILD FROM SCRATCH Take a look at the spectre log Two phases to a spectre build: Read the data by row Write the cbase by column Some errors will not crop up until write Test builds with limit input rows

15 CBASE IN PRODIVER Columns are defined by type, not by use By Default: String columns will be treated as dimensions Date (and Period ) columns will be treated as dimensions Double columns will be treated as summaries Integer and Fix100 columns will be treated as summaries and as dynamic dimensions

16 STEP 5: FIX DATA TYPES Take a look at your summary columns Take a look at Edit Dimensions In Workbench, change columns from Integer to String In Workbench, review Date and Period columns Integer vs Double vs Fix100

17 STEP 6: USING THE TEXT EDITOR Pack size should be a diveable dimension suggested-dimension attribute promotes (or demotes) columns in ProDiver Info fields are a good thing (sort of) Required-dimension attribute simulates info field relationships Strictly for convenience no integrity checking until dive. (But then, it s unforgiving!)

18 STEP 7: USE CBASE IN DIVEPLAN In Workbench, open /client-files/sales.dvp Save As sales_spectre.dvp Change the input from sales_consol.dvp to sales_build.cbase Save Open in ProDiver As long as the structure is right, it just works.

19 STEP 8: USE CBASE IN DIVEPORT In ProDiver, open sales_spectre.dvp Create a simple dive: Sales Manager, then Salesperson Save Marker /client-files/dive.mrk Create a simple report: Sales Manager + Salesperson Format as report Save Marker /client-files/report.mrk

20 STEP 8: USE CBASE IN DIVEPORT In DivePort, create a new page Add a measure portlet built on dive.mrk Add a quickview portlet to filter by sales manager Add a marker portlet built on report.mrk

21 NEW FEATURES VS COMPATIBILITY DivePlans and Markers on Spectre content provide compatibility with existing Model-based content. DiveTab requires Spectre files only. In the next hour, we re using DiveTab, so let s get ready for that!

22 SOME MORE NEW LINGO

23 STEP 9: DEFINE VIEW IN CPLAN In Workbench, open /spectre_example/sales.cplan.cplan,.dive, and.divetab do not have GUI editors (yet) Calcs are written in new expression language Timeseries can be defined as an object, or in individual calcs

24 STEP 10: DIVEPORT CONTENT In Workbench, open /spectre_example/salespeople.dive In Workbench, open /spectre_example/sales_managers.qvset In DivePort, create a new page Add a measure portlet based on salespeople.dive Add a quickview portlet based on sales_managers.qvset

25 FIND US DURING & AFTER THE SHOW: Blog LinkedIn Twitter Facebook