Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
So, I'm connecting to Essbase in PBI DT.
This query works:
SELECT
FILTER
(
[SCENARIO].Levels(2).Members,
SCENARIO.CurrentMember = [2020 ACTUAL]
)
On Columns,
NON EMPTY
CrossJoin(
{CrossJoin(
{CrossJoin(
{Members([TOTAL COST CENTERS].Levels(2))},
{Members([PERIOD].Levels(2))}
)},
{Members([ACTIVITY].Levels(1))}
)},
{Members([ACCOUNTS].Levels(2))})
On Rows
FROM PL.PL
But when I try to add a second expression to the FILTER function, I get:
Expression.Error: Essbase Error (1042017): Network error: Timed out before receiving all data
But I get that error IMMEDIATELY.
SELECT
FILTER
(
[SCENARIO].Levels(2).Members,
SCENARIO.CurrentMember = [2020 ACTUAL]
OR
SCENARIO.CurrentMember = [2019 ACTUAL]
)
On Columns,
NON EMPTY
CrossJoin(
{CrossJoin(
{CrossJoin(
{Members([TOTAL COST CENTERS].Levels(2))},
{Members([PERIOD].Levels(2))}
)},
{Members([ACTIVITY].Levels(1))}
)},
{Members([ACCOUNTS].Levels(2))})
On Rows
FROM PL.PL
What could possibly be going wrong?
Thanx so much in advance.
jrp
Hi, @pawlowski6132
I'd like to suggest you try to increase the 'Command timeout in minutes' when using essbase connector in Power BI Desktop. 'Command timeout in minutes' is a duration which controls how long the server-side query is allowed to run before it is canceled. The default value is ten minutes.
Essbase.Cubes(url as text, optional options as nullable record) as table
For further information, you may refer to the document .
Best Regards
Allan
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanx Allan, unfortunately, I have that set at 10 hours already.
As I mentioned, query doesn't even run for 1 second before erroring out.