DSA Data Source Standards

From DataSelf Knowledge Base
Revision as of 18:19, 9 October 2015 by Lwright (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Data Source Creation Process Checklist

SQL Views

tds (Data Source) Creation

tds Checklist

Creation Order

Create the InvoiceHeader.tds first. Then copy and rename it to Invoice.tds and change its connection to the lines SQL view. That way, the Header fields, hierarchies, and comments are already in place, don't have to be duplicated, and will be uniform to the user.

tds naming

Name the tds with the ERP/ModuleCode/Name: Sage 100 SA Sales Header.tds Sage 100 SA Sales.tds, Sage 300 AP Invoices.tds, Sage 500 AP Open Payables.tds etc

tds Hierarchies and Folders

In general, use hierarchies for dimension attributes, and then arrange the fields in logical order, for ease of discovery, and to allow mini-drilldowns within the larger structure.

Use folders for all non-core measures

Default Formats

Change date formats from DataTime to Date for most dates (except DataRefreshedAsOf)

Change measure formats to currency, no decimal, or percent, as appropriate

Field Comments

Add only the comments needed for fields that may be confusing to the user, such as where different addresses come from in the Sales Invoice.tds. Consider putting the comment on the hierarchy name, if appropriate. Otherwise, the comment popups get in the way.

Publishing to Server

Publishing a Data Source


Usually extracts will be published to DSA Server, with automatic refresh scheduling.


As the extract is being published, strip the ERP name from tds or tde name to be just ModuleCode/Name: Sage100 Sales.tds > Sage100 Sales.tde > SA Sales (on DSA Server).

This way, the OOTB sample reports will work for all packages without changing the source name.