Thanks for pointing that out. I think you are talking about this forgotten bug report in 6.0: https://bugs.launchpad.net/openobject-addons/+bug/713562
Still a solution is needed in 6.1. Having demo data that aren't as if they were generated by "Create Month period" of fiscal year make those data wrong :-/ As it is now we cannot test code with those data when we have to exclude opening entries. Maybe the config wizard should give a warning in case of demo data presence and erase those datas if present. (might be a big erasing dues to related data to descent though everything) Otherwise, if the purpose of demo data is to be present as the same time as real data a boolean could be needed in open-object to define if it is a demo data or not and having a separared context for each. Regards, Yannick -- You received this bug notification because you are a member of OpenERP Framework Experts, which is subscribed to OpenERP Addons. https://bugs.launchpad.net/bugs/924200 Title: [6.1] account demo data - wrong periods' definition for field special Status in OpenERP Addons (modules): Confirmed Bug description: Hello, In 6.1 revno 6453 In account/demo/account_demo.xml Demo data have no opening period and all periods are set to special. There must be 1 special (opening period) and 12 standard periods. Here is a patch to fix this. Regards, Yannick To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-addons/+bug/924200/+subscriptions -- Mailing list: https://launchpad.net/~credativ Post to : [email protected] Unsubscribe : https://launchpad.net/~credativ More help : https://help.launchpad.net/ListHelp
