Hi,
I have the following configuration:
-> Columns: Measures (Issues History) ; Status (Category)
-> Pages: Project (All projects by category)
-> Rows (Time)
When I select specific components in the project filter, if an issue has 2 components, it is counted 2 times.
So instead having, for eg. 10 issues in Done, I have 11 (9 issues with one component and one issue with 2 components).
I was trying to find a formula for distinct count, but without result.
Does somebody has any suggestions how can I display the right number?
Thank you
It seems my colleague Lauma already answered your inquiry in an internal conversation. Here is the proposed formula for all community members to see:
NonZero(Count(
Filter(
--go through individual issues
Descendants([Issue].CurrentHierarchyMember, [Issue].[Issue]),
IIF([Time].CurrentHierarchyMember is [Time].CurrentHierarchy.DefaultMember,
--if no period selected show distinct count of issues matching selected values
CAST([Measures].[Transitions to issues count] AS NUMERIC),
--count issues that had selected values at the end of period
DateBeforePeriodEnd(
[Issue].CurrentHierarchyMember.Get('Created at'),
[Time].CurrentHierarchyMember)
AND
[Measures].[Issues history] > 0
)
)))
The calculation is pretty demanding, as it iterates through Issue dimension “Issue” level members. Unfortunately, I don’t have any alternatives.
Upgrading to eazyBI 6.3.0 should not increase the report execution time by itself. However, upgrading eazyBI to a newer version might clear caches and increase initial report executions after an upgrade.
Do you still encounter query execution timeout errors? If so, please drop us a line at support@eazybi.com and share the definition of the report - Create reports.
But infortunately, i still have timeout errorwhen the number of issues is high or when i selected months or days level members.
In fact, our clients wanted this measure per days to use it during crisis time.
Even when i apply some filters, we should be able to provide to them a sufficiently flexible dashboard that they can use without having constant timeout when they select or not some filters.
Is there any way to improve the performance of the quiery?
