web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Errors when processing...
Microsoft Dynamics AX (Archived)

Errors when processing Demand Forecast cube

(0) ShareShare
ReportReport
Posted on by Maja RB 265

Hi,

I added some fields to Demand forecast cube and now I'm trying to process it. However, I keep getting errors which don't seem related to the fields that I added (I tried deleting the fields as well, didn't help).

The errors are all of this type (there are many more):

Errors in the high-level relational engine. The 'BASEENUM_CustVendorBlocked_18441' table that is required for a join cannot be reached based on the relationships in the data source view.

Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'CUSTTABLECUBE', Name of 'Customer' was being processed.

Errors in the OLAP storage engine: An error occurred while the 'Invoicing and delivery on hold' attribute of the 'Customer' dimension from the 'Demand Forecast initial' database was being processed.

 

Any ideas how to resolve this?

 

Thanks,

Maja

 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    venkatesh vadlamani Profile Picture
    venkatesh vadlamani 3,180 on at

    Go to BIGenerator class in AOT.

    Find the method generateAnalysisEnums()

    It tries to fill in a table for enums in different languages.

    Please truncate the same table and re run this method using a job.

    This should eliminate the enums error

  • Suggested answer
    venkatesh vadlamani Profile Picture
    venkatesh vadlamani 3,180 on at

    Correction of the method name  populateSRSAnalysisEnums()

  • Maja RB Profile Picture
    Maja RB 265 on at

    Thanks Venkatesh for the reply.

    Unfortunately, I can't confirm if your solution works cause in the meantime I managed to process the cube. I'm not sure what exactly worked cause I tried many things, but I think it was something along the lines of the solution described here:

    community.dynamics.com/.../129181

    So, I logged in as administrator, deleted the cube perspectives (SharedDimensions and ReqDemandPlaningCube), deleted the Visual studio project, compiled everything and tried processing the cube again. And it worked.

  • Suggested answer
    venkatesh vadlamani Profile Picture
    venkatesh vadlamani 3,180 on at

    That would also work for you, You have one enum which was not available even in EN-US, So when processing the same it throws this error.

    But if you follow the process mentioned in the  link you re do the entire set which includes this step.

    Regards

    Venkatesh

  • Maja RB Profile Picture
    Maja RB 265 on at

    Hi Venkatesh,

    I changed the AX language and tried processing the cube again (so that I get my desired language in the cube).

    Now I am getting errors again :(

    So I tried the procedure described above, but the errors are still here.

    I'm not sure which table I should truncate? Can I do that through AOT?

    Thanks,

    Maja

  • Suggested answer
    venkatesh vadlamani Profile Picture
    venkatesh vadlamani 3,180 on at

    Run the Wizard processing and deployment and select all the languages you need to support .

    Or create a record in UdmTranslation table which is referred in the method for the language you want to support.

    Do the same process as mentioned in earlier post

  • Suggested answer
    Lance [MSFT] Profile Picture
    Lance [MSFT] on at

    This sounds like a problem in the data source view.  

    'BASEENUM_CustVendorBlocked_18441' is a query to get values for an enumeration.

    It appears that somewhere there is an dimension that has an attribute which is set to use the values from this query, but there is a missing relationship in the data source view between the query for the dimension and this enumeration query, so ssas does not know how the two queries are supposed to join.

    My guess is the cube update process changed the name of the query, but either failed to update the dimension to use the new query name, or failed to update the data source view to link the new query to the dimension table.  Either way the query name in the dimension now doesn't match the name of any of the query as set in the CUSTTABLECUBE dimension.  To fix this, we need to make these settings match by updating either the dimension, or the data source view.

    There are two ways to fix this.

    Option A: update the dimension.

    Open the data source view and find CUSTTABLECUBE,

    check if it has a relation to a query with a name beginning with BASEENUM_CustVendorBlocked.  If no, go to option B.

    If yes, copy the name of that related query to clipboard.

    Open the dimension using CUSTTABLECUBE (probably named Customer).

    Find the attribute using the Blocked field (named Invoicing and delivery on hold)

    Expand the Name column property

    Expand the Source property

    Look at the TableID property value, which is probably set to 'BASEENUM_CustVendorBlocked_18441'  Replace this value by pasting in the name of the query copied above.

    Next expand the KeyColumns collection, and keep expanding the child elements until you've expanded the Source property and made the TableID property visible.  Replace the value by pasting in ihe name of the query copied above.

    Option B: update the data source view.

    open the data source view and find the data source view table for CUSTTABLECUBE.  Right click on it in the designer surface and add a new relation.

    Set the source table to CUSTTABLECUBE and the destination table to BASEENUM_CustVendorBlocked_18441

    Set the source column to BLOCKED and the destination column to ENUMITEMVALUE.

    Also check if the VENDTABLECUBE is also missing that relationship.  You might have a similar error there too.

    Save and redeploy the project.  Then process to see if there are any other failures.

    Hope this helps.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans