Forum Discussion
Data-Model Snag
Good Morning, Good Afternoon or Good Evening All o/
I have a testing data-model consisting of four tables:
- Calendar
- OrderID Key (Unique Records)
- Order Line Item Details
- Ancillary Order Info
The orders' market is stated as context on the Ancillary Order Info table while my revenue info is housed within the Order Line Item Details table. When I attempt to identify total billing my Market, I get the same value accross all markets. I have also attempted creating a markets key table like the OrderID's, but with the same result.
What am I doing wrong with the relationships/model?
Thank you for your advice and/or direction.
The Usurper
2 Replies
- amitchandakSuper User
I think those tables are still in Many to Many relation. All unique Order related information should be part of the order table
- DataUsurperHelper II
Thanks for jumping in to help, amitchandak. To confirm: you're suggesting I rehash my "AncillInfo" table for orderid duplicates, then and if/when I find/correct those use the AncillInfo table as my "market" legend selector rather than creating a unique records table/key?