"The data area could not be activated!" error in AppEngine

Had this working a few weeks ago but suddenly throwing an error. Wondering if its because my first element string is missing a dimension reference?

The data area could not be activated!, Error: 37, Cube: #GLTOT, Elements:("","CORE","CORE/11_NODE","CORE/(blank.)","CORE/89","CORE/16_NODE","CORE/(blank.)","CORE/14","CORE/20","CORE/60","CORE/17_NODE","CORE/(blank.)","CORE/87","CORE/88","CORE/1_NODE","CORE/(blank.)","CORE/10","CORE/11","CORE/12","CORE/14","CORE/15","CORE/20","CORE/21","CORE/22","CORE/40","CORE/45","CORE/60","CORE/81","CORE/83","CORE/85","CORE/87","CORE/88","CORE/2_NODE","CORE/(blank.)","CORE/10","CORE/11","CORE/12","CORE/14","CORE/15","CORE/20","CORE/21","CORE/22","CORE/40","CORE/45","CORE/60","CORE/81","CORE/83","CORE/87","CORE/88","CORE/89","CORE/31_NODE","CORE/(blank.)","CORE/45","CORE/3_NODE","CORE/(blank.)","CORE/5_NODE","CORE/(blank.)","CORE/10","CORE/15","CORE/20","CORE/21","CORE/45"),("","GLTOT_FinanceDimension1"),("","MyRole")

Code block:

    OLAPConnection olapCon = OLAPCreatePooledNamedConnection(sAlias);
    OLAPElement entpar = OLAPGetDimensionElement(olapCon, sDim, sEntTop);
    OLAPElementList EntityList = CreateOLAPElementList();
    OLAPElementList EntityList2 = CreateOLAPElementList();
    OLAPElementListAddElement(EntityList, entpar);
    EntityList2 = OLAPGetChildElementList(olapCon, sDim, sEntTop, false);

    foreach (OLAPElement el in EntityList2)
    {
        NotifyDebug("Adding Element: "+ el);
        OLAPElementListAddElement(EntityList, el);
    }

    OLAPDataArea cubeVals = OLAPCreateDataArea(olapCon, sCube, OlapDataAreaIncludeB, OlapDataAreaOperatorNone, 0.0, OlapDataAreaOperatorNone, 0.0 ,EntityList, sFD1, sGroup);

Find more posts tagged with

Infor EPM Discussions

Comments

Martin Reischl

Hi Matthew,

the empty strings at the beginning of the string lists are fine, they are reserved for the * or B or C entries for all elements, base-level elements, or calculated-level elements. (They used to be good for subset names too but I have the impression that this is no longer the case)

Error 37 means "element not found", so some of your elements is missing. Since you are reading the long list straight from the dimension, the suspects are "GLTOT_FinanceDimension1" in dimension 2 and "MyRole" in dimension3. This looks like a 3-dimension MDAC cube, is this correct?

Best Regards

Martin

dEPM-631 - How to get data into Infor dEPM - S01E02_ - Journey from Data Lake to OLAP_.mp4

Legacy Contributor

2 dimension MDAC Cube, "MyRole" is the OLAP Data Role Im attempting to secure.

BTW, how do you know error 37 is "element not found"? Is there a reference somewhere that I could use in the future?

Martin Reischl

You can find the error codes in the documentation, in the OLAP SDK section:

https://docs.infor.com/depm/2023.x/en-us/depmolh_cloud/default.html?helpcontent=olap_sdk_cloud/rwu1510174494712.html

Martin

Wichtige Lösungen in der Wissensdatenbank April 2013.pdf

Legacy Contributor

that error doesnt make sense because all those values are valid cells. so my OLAPCreateDataArea call must be constructed wrong. #GLTOT is a 2 dimension MDAC cube. GLTOT_FinanceDimension1 and AccountingEntity. sGroup is the current OLAP Data Role that im creating the data area for. any idea why that wouldnt be valid?

Legacy Contributor

Ok, figured it out. The issue was twofold:

I had the wrong value set for my EntityList. I was setting that as the string name for the dimension and it needs to be the element to add to the Data Area.
Order is imperative. In my case I was using an MDAC cube so the order was the AccountingEntity, FinanceDimension1 and Roles.

The big blocker there was the idea that the role is actually a dimension. I wasnt thinking of it in that way.

This routine still isnt getting me what I need, but at least its working from a functional standpoint (i see another post in my near future).

Thanks Martin.

Copyright © 2025 Infor. All rights reserved.