Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

This document assumes you are familiar with Shoplogix Event data.

Events Data are now live (Release date: April 16, 2021) in Analytics.

Due to the many-to-many nature of the primary [Fact Core] to [Fact Events] relationship, many uses of the Fact Events table are not valid with our [Fact Core]-centric model.

The following joins are valid:

  • [Dim Machines]

  • [Dim Dates]

the following joins are INVALID:

  • [Dim Jobs]

  • [Dim Shift Instances]

  • [Dim Recent Shifts]

Attempting the invalid joins will duplicate results and give confusing results. The supported use cases for Events are:

  1. Event Pareto: All occurrences, durations, and average duration

    1. Filterable by Machine Name and Calendar DateTime.

    2. Note any correlation to Shift or Job is best achieved by identifying time ranges and filtering to those. Shifts and Jobs not at the hourly level will not be able to perfectly correlate.

Totally reasonable thing to ask for, but not currently possible, is “show me all the event durations for these 3 shifts.” We may be able to build enhancement to support this. CS-Eng, please add a comment and tag Steven Arrol (Unlicensed) Ben Patterson (Unlicensed) to draw attention to your need.

Historical Events Data

Events are saved for 60 days.

They can be exported from the exportapi if events older than 60 days are required.

More Info

Engineers, here is the full background in context of Analytics: https://slxdev.atlassian.net/browse/PROD-244

  • No labels