Skip to main content

How to add financial dimensions to cubes [AX 2012]

AX 2012 BI is so much easier and enjoyable to use. Seeing how easy it is, I don’t see a reason for not deploying it all clients.

To add a financial dimension
  1. Click Tools > Business Intelligence (BI) tools > SQL ServerAnalysis Services project wizard. Click Next.

  2. Select Update and then click Next.

  3. Select an Analysis Services project to add the financial dimension to, and then click Next. After the project builds, click Next again.

  4. On the Select perspectives screen, click Next.

  5. On the Select Microsoft Dynamics AX dimensions screen, select financial dimensions you want to include in your Analysis Services project.

  6. Complete the wizard.

Cube2012-07-18_0959

Cube2012-07-18_1000

Cube2012-07-18_1001

Select the perspectives

Cube2012-07-18_1002

Select the dimensions

Cube2012-07-18_1003

Select the date diemension/s

Cube2012-07-18_1004b

Select the label translations

Cube2012-07-18_1004c

Then wait for it to finish. This will take some time.

cubes2012-07-18_1005

Once done. Continue with the wizard.

c2012-07-18_1042

 

By the selections we made in the wizard. The “Visual Studio Projects” > “Analysis Services Project” > “Dynamics AX” in the AOT is modified to include the changes.

Final result. My dimensions are available in the cube now.

C2012-07-18_1229

 

Interesting video on BI story in AX 2012

http://www.youtube.com/watch?v=2XKZibvK2cQ

 

Reference:

http://msdn.microsoft.com/EN-US/library/hh128830

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...