From 9b4da889a1d19dc68bebd3a98bdce6c08aeb4fe0 Mon Sep 17 00:00:00 2001
From: mreficent <miquel.raich@eficent.com>
Date: Fri, 19 Jul 2019 13:18:41 +0200
Subject: [PATCH] [ADD] fiscalyear date.range.type data

This date.range.type in v11 have benn used in some cases. Then, when you migrate, you need to have this data or else delete its xmlid.

We think it's better to keep it, because you may want to still use it.
---
 account_fiscal_year/__manifest__.py          | 1 +
 account_fiscal_year/data/date_range_type.xml | 7 +++++++
 2 files changed, 8 insertions(+)
 create mode 100644 account_fiscal_year/data/date_range_type.xml

diff --git a/account_fiscal_year/__manifest__.py b/account_fiscal_year/__manifest__.py
index 9efe49945..9795a889d 100644
--- a/account_fiscal_year/__manifest__.py
+++ b/account_fiscal_year/__manifest__.py
@@ -19,6 +19,7 @@
         "date_range",
     ],
     "data": [
+        "data/date_range_type.xml",
         "views/account_views.xml"
     ],
 }
diff --git a/account_fiscal_year/data/date_range_type.xml b/account_fiscal_year/data/date_range_type.xml
new file mode 100644
index 000000000..74137767a
--- /dev/null
+++ b/account_fiscal_year/data/date_range_type.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<odoo>
+    <record id="fiscalyear" model="date.range.type">
+        <field name="name">Fiscal Year</field>
+        <field name="allow_overlap" eval="False"/>
+    </record>
+</odoo>