Issues with two fact tables that share one dimension
I have an issue with two fact tables connected to one date dimension. The two fact tables have ranges of different dates, but all dates are present in the date dimension.
I encounter the problem when I try to process the cube, I get an error stating that my date dimension does not have a FK for dates that I know are in the dimension. See the illustration below:
Only when my two fact tables share the same date ranges will my cube process. If either cube has any dates that are not in the other, then the process fails.
Has anyone encountered this issue?
I found the culprit causing the cube process to fail. There was a filter applied to the date dimension in the DSV that I had fogotten about. Removed the filter and the cube processed with no issue.
That was a painful reminder of keeping trouble shooting simple.
- What is the real difference between an API and an microservice?
- Do you know any alternative to NDepend for architects?
- Xcode 12 Apple M1 arm64 - Designable error: "wrong architecture"
- Building a minimal plugin architecture in Python
- Cross module communication in modular monolith
- Software design for simultaneously running python programs
- Proper design for th Keycloak auth with APIs and UI
- "Aggregator microservice" or just gateway api?
- Macro definition to determine big endian or little endian machine?
- Angular Service Injection in reusable components
- Offset pagination vs Cursor pagination
- With the MESI protocol, a write hit also stalls the processor, right?
- Architecture design for divide the subsystems
- Solution/Architecture: queues or something else?
- How functional approach of web app architecture looks like?
- Prevent duplicate messages
- The better way to read a formated data from .TXT file strings in Python
- Building app and Anti pattern (distributed monolith...)
- Effective Backend for Real Estate Application
- In which place is it better to create kafka topics programmatically?
- What's the relationship between assembly language and machine language?
- Logging out: GET or POST?
- Architectural question - how to avoid multiple events tobe processed at the same time
- Layered architecture, Request and Response DTO, or View Models
- Interfaces and errors in go
- How to Implement Queue Based Workflow System?
- "Microservices Using Database Per Service" pattern in practice
- Handling Multiple Actors in a Use Case in Clean Architecture and DDD
- Should services always return DTOs, or can they also return domain models?
- When do I call my class controller, manager or service?