Cognos FM 雪花型还是星型模式？需要有关层次结构的帮助
我需要一些有关 Cognos Framework Manager 8.4 中建模的帮助。 给定以下模式
其中
- F_sales.order_key 引用 D_order.sid
- D_orderItems.orderID 参考 D_order.OrderID
- D_productAttributes.OrderItemID 引用 D_orderItems.orderItemsID
通过 Cognos Report Studio 创建报告时，我无法过滤具有 attributeKey（例如“shippingType”和 attributeValue“Standard”或“Express”或其他）的 orderItems 的订单。
我猜问题出在准 m:n 关系上。实际上这应该不是问题。所以我认为解决方案是在框架管理器中创建一个常规维度，其层次结构如下 “一个订单可以包含多个订单项目，每个订单项目都有多个 attributeKeys 和 -values”
这是解决方案吗？我将如何做到这一点？有人可以指导我吗？
还是这样可以，但我在 Report Studio 中遗漏了一些东西？在我的测试中，我刚刚创建了一个列表，其中包含事实表中的事实和 D_order 中的 orderID。过滤其他所有内容都工作正常，但过滤例如 D_productAttributes.attributeValue = 'Express' 时没有任何效果
提前致谢。
I need some help with modeling in Cognos Framework Manager 8.4.
Given following schema
where
- F_sales.order_key references
D_order.sid - D_orderItems.orderID references
D_order.OrderID - D_productAttributes.OrderItemID
references D_orderItems.orderItemsID
When creating reports via Cognos Report Studio I am not able to filter for orders which have orderItems which have attributeKey e.g. 'shippingType' and attributeValue 'Standard' or 'Express' or whatever.
I guess the problem is the quasi m:n relationship. In practice this shouldn't be a problem. So I thought a solution would be to create a regular dimension in framework manager with a hierarchy like
"An order can consist of multiple order items and each order item has multiple attributeKeys and -values"
Is this the solution and how would I do that? Can someone guide me, please?
Or is it okay like it is and I am missing something in Report Studio? In my test I just created a list which has the facts from fact table and orderID from D_order. Filtering for everything else works fine, but there is no effect when filtering for e.g. D_productAttributes.attributeValue = 'Express'
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
问题解决了。答案不是常规的维度和层次结构。当我保持关系不变并创建模型查询主题时，它会起作用。不需要决定因素。 为 orderItems 创建了一个模型查询主题
D_orderItems)
与 D_productAttributes 相同，但使用
然后我通过 sid 将两个模型查询主题连接到我的事实表。创建用于构建报告的包时，我将 D_orderItems 和 D_productAttributes 完全保留，因此它们在 Report Studio 中不可见。就像魅力一样。
Problem solved. The answer is not regular dimension and hierarchy. It works when I leave the relationships as they are and create model query subjects. No determinants needed. I created one model query subject for orderItems with
D_orderItems)
Same for D_productAttributes, but with
Then I joined the two model query subjects to my fact table via sid. When creating the package for building reports I leave D_orderItems and D_productAttributes completely out, so they are not visible in report studio. Works like a charm.