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.
Thanks for pointing that out.
I think you are talking about this forgotten bug report in 6.0: /bugs.launchpad .net/openobject -addons/ +bug/713562
https:/
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