Data Module shortcuts should inherit target navigation paths

Shortcuts are a new feature within a Data Module.

Shortcuts should inherit all the attributes of the target object. For example, I can create a shortcut to the Product dimension. The product dimension can be included within a navigation path.

Any shortcuts to the product dimension cannot use the product dimensions navigation path! You have to create new navigation paths for each product shortcut.

If you use shortcuts to simulate star schema groupings, you would end up with a product dimension shortcut for every fact table.

Imagine how complex the navigation path interface will become.

Currently, the only reason to use data modules above FM is for navigation paths. This flaw on shortcuts not being able to use the targets navigation path means we cannot use shortcuts.

We desperately need to use shortcuts to simplify complex data modules built on an enterprise data warehouse.

For example. I define a navigation path on PRODUCT.LINE -> PRODUCT.TYPE -> PRODUCT.NAME.

I create two shortcuts to PRODUCT, one for use on the sales fact, and another for use on the returns fact: PRODUCT_SALES, PRODUCT_RETURNS.

Within a dashboard I create a graph of PRODUCT_SALES and SALES. This chart cannot drill down as no navigation path is defined. I have to define PRODUCT_SALES.LINE -> PRODUCT_SALES.TYPE -> PRODUCT_SALES.NAME.

And the same on returns PRODUCT_RETURNS.LINE -> PRODUCT_RETURNS.TYPE -> PRODUCT_RETURNS.NAME.

When the user opens the navigation path interface they now have three product navigation paths to choose from! If they choose the wrong one then they could end up with a multifact query.

I understand why this is complex - as shortcuts have their own Id that isnt related to the target. But that is another issue for another day.

Navigation paths must still be capable of taking objects from different queries.