Naming Guidelines
Object | Guideline | Notes | Good Example | Bad Example |
---|---|---|---|---|
Data Sources | A-Z a-z _, <space>, Numbers | Must be usable from DATA() functions. Avoid putting version information in the name and use the description instead. | SALES_DATA_PRODUCTION, "GEM Data" | |
Dimension & Levels | A-Z a-z _ | Since level names are automatically matched, the levels should adhere to the same rules as Excel Column names. | Location, Product_D, PRODUCT_D, PRODUCT, PRODUCT_CODE | Product-Code, 123Dim |
Excel Worksheets | A-Z, a-z, _ , no Numbers, no Spaces Append _DIM for Dimension Sheets | Must be usable from DATA() functions. Valsight translates the Names to internal database names, therefore stricter rules than in Excel apply. | Sales, FTEs | 2018-Products, Products-V1 2018-03 |
Excel Column Names | A-Z, a-z no Numbers, no Spaces, underscore is OK. | Valsight translates the Names to internal database column names, therefore stricter rules than in Excel apply. | Volume, Number_of_Units_Sold | "Number of FTEs" |
Excel Filename | The filename has no implications for Valsight, as the Data Source name is used to access the file. |