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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Customize AX 2012 Date Dimension in Default Cubes

(0) ShareShare
ReportReport
Posted on by

I am working in Dynamics AX 2012 R3.  I would like to extend the Date functionality in the Default Cubes.  Specifically, I would like the new field to appear in the Date dimension when the SSAS project is generated by AX using the SSAS project wizard. 

I was able to successful add a new field to the BIDateDimensionValue table, include in the BIDateDimensionsView, and populate via the BIDateDimensionManager class' populateDateDimensionValues method.  I see that my new field is included in the generated Data Source View for the cube; however, it is not added as a Dimension Attribute for the actual date dimension(s).

Can anyone provide direction on how to have this field added to the Dimension Attributes?  How does the cube generator determine which fields to include?  I assume there must be some place where there is a definition that allows the attribute key, label, and name values to be configured.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Lance [MSFT] Profile Picture
    on at

    Normally the analysis services project generator determines which fields to create as attributes based on a property value AnalysisUsage on the perspective view or table fields, which should be set to Attribute if the field is to be used as an attribute, or measure if the field is to be used as a measure.  

    But the problem here is that dimension definition for Date dimension is hard coded, so there's no way to change the default date dimension through the perspective settings.  

    For this case, I would edit the analysis services project in SqlDataTools and add a new Dimension attribute to the Date.dim dimension file and set the new attribute to use your new field as its key field.  Then deploy and process the updated project.

    Hope this helps,

    -- Lance.

  • Community Member Profile Picture
    on at

    My concern with this approach is that any updates via the SSAS project wizard would overwrite the changes.  I know that custom calculations can be preserved by importing the modified SSAS project back into the AOT, but I suspect this change would be lost.  I was hoping there was an XML definition somewhere that I could modify.  Regardless I can take this approach.  Thanks for the response!

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…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
Ali Zaidi Profile Picture

Ali Zaidi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans