To GoodData homepage

Knowledge base
AnalyticsDashboards and Reports - KB articles8 Metrics and MAQL - KB articles23
Data modeling & IntegrationData models - KB articles9 Data sources - KB articles9
Development & AdministrationGoodData.UI - KB articles12 Administration - KB articles18 Solution architecture - KB articles8 SDKs and APIs - KB articles9
Community
WelcomeAbout GoodData13
AnalyticsDashboards and Reports161 Metrics and MAQL107
Data modeling & IntegrationData models35 Data sources69
Development & AdministrationGoodData.UI38 Administration86 Solution architecture13 SDKs and APIs28

Ask your question
Login

Community
Search

Replies posted by Jay Finegan

7 Replies

Newest first

Oldest first

Jay FineganParticipating Frequently

asked in Metrics and MAQL

Counting records by metric

Unfortunately, that solution does not work for me. I think the issue lies in mutilple date dimensions in play: Date (Event) and Date (Date of Hire). If I’m correct, we’ll have to rethink our data model accordingly to turn the length-of-service bucket into an attribute.

Jay FineganParticipating Frequently

asked in Metrics and MAQL

Counting records by metric

That looks like it might work, but I might not be able to test it for a day or so. Thanks.

Jay FineganParticipating Frequently

asked in Metrics and MAQL

Counting records by metric

The problem is that both the calculated length of service and the bucket are metrics, not attributes. the BY feature only works with attributes.

Jay FineganParticipating Frequently

asked in Metrics and MAQL

RUNSUM doesn't seem to like intermittent data

Issue solved! I found a way to do this without passing a zero value. It’s a three-step process (some of which could probably be combined):Use SELECT to aggregate records (assume my metric is called RecordCount) Create an IF-THEN-ELSE metric (SELECT IF RecordCount > 0 THEN RecordCount ELSE 0 END; assume my metric is called IfThen) Create a RUNSUM metric (SELECT RUNSUM(IfThen))In the following chart, notice how, in the first row, the hours increased between Feb and March but YTD Rec Count did not. Previously, because there were no incidents in March, I would get a dash and the YTD TRIR would not calculate. Now I get values!

Jay FineganParticipating Frequently

asked in Metrics and MAQL

RUNSUM doesn't seem to like intermittent data

Hi, Joseph, We are counting injuries to employees - naturally we prefer not to have any. We normally pass data surrounding actual incidents. It sounds like you are saying that if we don’t have any incidents in a given month, we need to pass a zero value for that month. Am I understanding your statement correctly?

Jay FineganParticipating Frequently

asked in Metrics and MAQL

Single dashboard, two KPIs, use a different time frames

Here is a screen capture of a dashboard:As you can see from the three KPIs at the top right, the system clearly understands the values which represent the end of my timeline, the start of the timeline per the Date Range filter (30 days less than the end), and a value 365 days prior to the end of my timeline.What I don’t understand is why the system is able to count incidents which occur between _Timeline_Start and _Timeline_End but not incidents which occur between (_Timeline_End - 365) and _Timeline_End. Here are the relevant metric definitions:_Timeline_Start: SELECT MIN(Date (Timeline)) BY ALL OTHER WITHOUT PF EXCEPT Date (Timeline)_Timeline_End: SELECT MAX(Date (Timeline)) BY ALL OTHER WITHOUT PF EXCEPT Date (Timeline)The 1-month count: SELECT IFNULL(COUNT(incidentID),0) WHERE isRecordable=1 AND Date (Event) BETWEEN _Timeline_Start AND _Timeline_EndThe 12-month count: SELECT IFNULL(COUNT(incidentID),0) WHERE isRecordable=1 AND Date (Event) BETWEEN (_Timeline_End - 365) AND _Timelin

Jay FineganParticipating Frequently

asked in Metrics and MAQL

Single dashboard, two KPIs, use a different time frames

Yes. While we might anticipate that a given person would set the end date of the dashboard filter to be the most recent full month (e.g., since today is 8/19/2022, we would anticipate that the user would probably set the filter end date to July 31, 2022). But a user should remain free to change the filter, such that if this were to happen, both the 12-month period and the previous month should update consistent with the new end date. I’m glad that you think it’s doable - I’m eager to see how it would be down. This is a fairly common request in our industry.

Powered by Gainsight

Welcome to the GoodData Community!Cookie settings

Sign up

Already have an account? Login

Social Login

or

Username (also your display name - please use John Doe rather than john.doe) *

E-mail address (if you already use GoodData, we encourage you to use the same e-mail address you use for the GoodData platform) *

Full Name

(Private)

Only you and moderators can see this information

*

Company

(Private)

Only you and moderators can see this information

*

I use the following GoodData products

(Private)

Only you and moderators can see this information

GoodData Platform GoodData Cloud GoodData.CN

Password *

I have read and agree to the GoodData Community and University Terms of Use and Privacy Policy.

loginBox.register.email_repeat

Login to the community

Sign in with your community account. This is different than your login to your GoodData account. Don't have a community login? Create an account

Social Login

or

Username or Email

Password

Remember me

Forgot password?

Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.

Username or e-mail

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

OK

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

OK