I think it should be possible, as Sales Header could be a Dimension connected with Document Type, Document No.
However... if it's not too late, I'd advise against BA. We spent weeks trying to configure it and finally gave up. It's too fragile. F.e. whenever we have a dimension value that has no entries associated as yet - like a new Item that has no transactions yet - it crashed.
BA is just a frontend for configuring MS SQL Analysis Services. It's only useful if you have a native database as it sets up DTS packages for exporting the data to and SQL database. If your Navision is already running on SQL server, then you only need to generate a Date table in SQL to use with Date dimensions and basically everything else is a Next/Next/OK setup with star or sometimes snowflake dimensions and setting relations in Analysis Services and it just works. It has no flowfields of course, but that's not a big problem, you just need to always uses the lowest level fact tables (Detailed Customer Ledger Entry and so on).
Comments
Can you explain more what you meant by this? When you say cube, do you mean a matrix box?
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
However... if it's not too late, I'd advise against BA. We spent weeks trying to configure it and finally gave up. It's too fragile. F.e. whenever we have a dimension value that has no entries associated as yet - like a new Item that has no transactions yet - it crashed.
BA is just a frontend for configuring MS SQL Analysis Services. It's only useful if you have a native database as it sets up DTS packages for exporting the data to and SQL database. If your Navision is already running on SQL server, then you only need to generate a Date table in SQL to use with Date dimensions and basically everything else is a Next/Next/OK setup with star or sometimes snowflake dimensions and setting relations in Analysis Services and it just works. It has no flowfields of course, but that's not a big problem, you just need to always uses the lowest level fact tables (Detailed Customer Ledger Entry and so on).