Originally created by: grynn-in
Closes [#78].
The seed is realistic D365 reference data — most rows are entities not in the demo (CN01->Fiscal_CN, MYMF->Fiscal_MY, …) whose calendars aren't loaded. They're inert (no GL activity) and intentionally retained as a multi-calendar template. Flattening them all to Standard would destroy that reference value and be semantically wrong (a China entity isn't on a 'Standard' calendar), so I didn't do that.
Fisscal_IN -> Fiscal_IN (DAIN, INMF)._seeds.yml description documenting the reference-data nature and the invariant that active entities must reference a loaded calendar.The real risk [#78] raised — an inert entity gaining GL data while pointing at a missing calendar — is now caught by #77's assert_fiscal_calendar_is_loaded (scoped to active entities), which fails the build instead of silently falling back. So the inert reference rows are safe to keep.
If you'd prefer a fuller cleanup (trim non-demo entities, or load the other calendars' period data), say so and I'll follow up — those are the issue's option (a)/(trim) paths.
Pairs with [#77]. Verified: dbt seed --select entity_fiscal_calendars -> PASS, yml parses.
Ticket changed by: grynn-in