Appendix: Datasets and Dataset types

1. Naming Conventions

Datasets follow specific naming convention helping users to identify them easily as follows:

  • A standard prefix (e.g. Planning for cammsstrategy datasets) and suffix _STND (e.g. Planning_ActionDetails_STND) denoting that this is a standard dataset provided by CAMMS.

  • If any custom datasets are provided to your organisation, they will include an abbreviation of your organisation as a suffix in place of _STND (e.g. Planning_ActionInfo_DELWP).

  • Datasets will be grouped by product category e.g. all cammsstrategy related datasets will be grouped under the 'Planning' category although these can be changed by your Administrator.

  • Certain datasets while homed within a particular category may yet be applicable across products e.g. Planning_SystemPeriod_STND, Planning_OrgHierarchy_STND etc.

2. Dataset design

The key dataset for each element e.g. Planning_ActionDetails_STND, Planning_KPIDetails_STND will not repeat the same action or KPI twice as they only include single value information. Where a record has multiple values, these have been provided as additional datasets e.g. while Planning_ActionDetails_STND can give you a snapshot of Action data including its % Complete and Commentary in its current state, the Planning_ActionProgress_STND dataset offers all such progress information over the different reporting periods. This allows you to generate a line chart of Action Target vs Actual % Complete as it progressed over the months or quarters for example.

Datasets are also designed to always display any custom labelling* you have configured within the respective product e.g. if Business Unit is labelled as 'Department' within your cammsstrategy application, it will appear as Department within your cammsinsights as well. 

Some fields are parameterised and only used by some organisations. Thus, certain fields which are not used within your CAMMS product may yet appear within your datasets e.g. Action Revised Dates are not activated for all organisations and thus will not hold any values if not activated for you. Please contact your Insights Administrator if such fields appear as they can hide any datasets or fields that are not relevant for your organisation.

*This does not apply to ID type fields so for example, BUSINESSUNITID would appear as is and will not reflect your custom label of Department.

3. Automatic Dataset Establishment

Certain applications such as cammsincident and cammsproject allow you to create a large number of custom objects and tables. The common datasets for these (Incident_CustomObject_STND, Incident_CustomTable_STND, Project_CustomObject_STND and Project_CustomTable_STND) cater for these objects by enabling you to pull data from any of the respective objects and tables and simply filtering to ensure you are getting the data from the one you want. However, we have also established a facility by which you can create standalone datasets for each object/table as per your preference through the respective applications. Please find details of this below:

4. Datasets for cammsincident Custom Objects/Tables

Look for the dataset creation icon in your Custom Object (non standard object) or Custom Table Configuration Details screen as shown below. Click it to create the dataset.

Figure 4.1
Figure 4.2

5. Datasets for cammsproject Custom Objects/Tables

Look for the Create Insights Dataset button in your Custom Object or Custom Table Configuration screen as shown below. Click it to create the dataset.

IMPORTANT: Don’t forget to remind your Insights Administrator to perform a dataset update and make these newly created datasets available to your user role in order to use these newly established datasets when creating new reports within the Insights application.

6. Other considerations

  • If you add or change or edit the visibility and/or label of a field you will have to ask your Insights Administrator to perform a dataset update before you can see these changes reflected in your datasets. Furthermore, if you had created a report using a label which is now renamed, edited or removed, the report would have to be edited and saved again to ensure that it can run properly.

  • Similar to above, you should also ensure that you do not label two fields with the same name – this will prevent your data model from picking up the dataset fields correctly.

  • Above also applies to fields that CAMMS have used as a fixed field in your dataset e.g. your project details dataset has a fixed field called ‘Project Workflow’. If you by chance rename another field in your project details object with this label, your field will not appear in the Insights dataset. Therefore, always ensure you use unique labels.

  • If you have entered a line break in any text type field, this will prevent you from filtering for this value in Insights.