Public bug reported: A few things going on here:
TL:DR 1. Dataset export does not contain the <dataEntryForms> tag as a child <metaData>. 2. Dataset uploads with <dataEntryForm> as a child of <dataSet> has no effect on the custom form 3. Dataset uploads with <dataEntryForms> as a child of <metaData> with matching entry under <dataSet> still has no effect on custom form Long Form: 1. I'm not sure where the intended location of the dataEntryForm custom HTML. If it is supposed to live as a child of <dataSet>, then all is fine. If it is supposed to live in <dataEntryForms> with a link to it in <dataSet> as I suspect, then exporting the dataSet should probably come with the <dataEntryForms> even if "Export With Dependencies" is _not_ checked. It is also strange to see the custom HTML twice when you do export with Dependencies. Which one is correct? It can also constrain a questionable connection if the custom form is very large, as the xml file is now doubled in size. 2. If I alter an exiting custom form in the <dataSet> section and try to upload the xml for it, it will not have any affect. See the video of this in action and the link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. 3. As above, if I alter an exiting custom form in the <dataEntryForms> section of the xml file, and try to upload the xml for it, it will not have any affect. See the video of this in action and the link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. Steps to Reporduce: 1. Log in as superuser 2. Download the following xml files, alter the name,shortname,code,uid and upload to playdemo 3. Make a an additional change to the custom form and upload to play demo, notice nothing actually changes. Without the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMcHlIalZTcUNGWkk With the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMRTNHanNYbmJGUFk Video In Action: https://drive.google.com/open?id=0B9eJ8PZ_4csMYmtYWnJJN1Rtc2M ** Affects: dhis2 Importance: Undecided Status: New ** Description changed: A few things going on here: TL:DR 1. Dataset export does not contain the <dataEntryForms> tag as a child <metaData>. 2. Dataset uploads with <dataEntryForm> as a child of <dataSet> has no effect on the custom form 3. Dataset uploads with <dataEntryForms> as a child of <metaData> with matching entry under <dataSet> still has no effect on custom form Long Form: - 1. I'm not sure where the intended location of the dataEntryForm custom HTML. If it is supposed to live as a child of <dataSet>, then tall is fine. If it is supposed to live in <dataEntryForms> with a link to it in <dataSet> as I suspect, then exporting the dataSet should probably come with the <dataEntryForms> even if "Export With Dependencies" is _not_ checked. It is also strange to see the custom HTML twice when you do export with Dependencies. Which one is correct? It can also constrain a questionable connection if the custom form is very large, as the xml file is now doubled in size. + 1. I'm not sure where the intended location of the dataEntryForm custom HTML. If it is supposed to live as a child of <dataSet>, then all is fine. If it is supposed to live in <dataEntryForms> with a link to it in <dataSet> as I suspect, then exporting the dataSet should probably come with the <dataEntryForms> even if "Export With Dependencies" is _not_ checked. It is also strange to see the custom HTML twice when you do export with Dependencies. Which one is correct? It can also constrain a questionable connection if the custom form is very large, as the xml file is now doubled in size. 2. If I alter an exiting custom form in the <dataSet> section and try to upload the xml for it, it will not have any affect. See the video of this in action and here is a link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. 3. As above, if I alter an exiting custom form in the <dataEntryForms> section of the xml file, and try to upload the xml for it, it will not have any affect. See the video of this in action and here is a link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. Steps to Reporduce: 1. Download the following xml files, alter the name,shortname,code,uid and upload to playdemo 2. Make a an additional change to the custom form and upload to play demo, notice nothing actually changes. Without the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMcHlIalZTcUNGWkk With the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMRTNHanNYbmJGUFk Video In Action: https://drive.google.com/open?id=0B9eJ8PZ_4csMYmtYWnJJN1Rtc2M ** Description changed: A few things going on here: TL:DR 1. Dataset export does not contain the <dataEntryForms> tag as a child <metaData>. 2. Dataset uploads with <dataEntryForm> as a child of <dataSet> has no effect on the custom form 3. Dataset uploads with <dataEntryForms> as a child of <metaData> with matching entry under <dataSet> still has no effect on custom form Long Form: 1. I'm not sure where the intended location of the dataEntryForm custom HTML. If it is supposed to live as a child of <dataSet>, then all is fine. If it is supposed to live in <dataEntryForms> with a link to it in <dataSet> as I suspect, then exporting the dataSet should probably come with the <dataEntryForms> even if "Export With Dependencies" is _not_ checked. It is also strange to see the custom HTML twice when you do export with Dependencies. Which one is correct? It can also constrain a questionable connection if the custom form is very large, as the xml file is now doubled in size. 2. If I alter an exiting custom form in the <dataSet> section and try to upload the xml for it, it will not have any affect. See the video of - this in action and here is a link to the xml file I'm using to do this - on the play demo site. This behavior is the exact same for 2.23, where I - first encountered it. + this in action and the link to the xml file I'm using to do this on the + play demo site. This behavior is the exact same for 2.23, where I first + encountered it. 3. As above, if I alter an exiting custom form in the <dataEntryForms> section of the xml file, and try to upload the xml for it, it will not - have any affect. See the video of this in action and here is a link to - the xml file I'm using to do this on the play demo site. This behavior - is the exact same for 2.23, where I first encountered it. + have any affect. See the video of this in action and the link to the xml + file I'm using to do this on the play demo site. This behavior is the + exact same for 2.23, where I first encountered it. Steps to Reporduce: 1. Download the following xml files, alter the name,shortname,code,uid and upload to playdemo 2. Make a an additional change to the custom form and upload to play demo, notice nothing actually changes. Without the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMcHlIalZTcUNGWkk With the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMRTNHanNYbmJGUFk Video In Action: https://drive.google.com/open?id=0B9eJ8PZ_4csMYmtYWnJJN1Rtc2M ** Description changed: A few things going on here: TL:DR 1. Dataset export does not contain the <dataEntryForms> tag as a child <metaData>. 2. Dataset uploads with <dataEntryForm> as a child of <dataSet> has no effect on the custom form 3. Dataset uploads with <dataEntryForms> as a child of <metaData> with matching entry under <dataSet> still has no effect on custom form Long Form: 1. I'm not sure where the intended location of the dataEntryForm custom HTML. If it is supposed to live as a child of <dataSet>, then all is fine. If it is supposed to live in <dataEntryForms> with a link to it in <dataSet> as I suspect, then exporting the dataSet should probably come with the <dataEntryForms> even if "Export With Dependencies" is _not_ checked. It is also strange to see the custom HTML twice when you do export with Dependencies. Which one is correct? It can also constrain a questionable connection if the custom form is very large, as the xml file is now doubled in size. 2. If I alter an exiting custom form in the <dataSet> section and try to upload the xml for it, it will not have any affect. See the video of this in action and the link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. 3. As above, if I alter an exiting custom form in the <dataEntryForms> section of the xml file, and try to upload the xml for it, it will not have any affect. See the video of this in action and the link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. Steps to Reporduce: - 1. Download the following xml files, alter the name,shortname,code,uid and upload to playdemo - 2. Make a an additional change to the custom form and upload to play demo, notice nothing actually changes. + 1. Log in as superuser + 2. Download the following xml files, alter the name,shortname,code,uid and upload to playdemo + 3. Make a an additional change to the custom form and upload to play demo, notice nothing actually changes. Without the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMcHlIalZTcUNGWkk With the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMRTNHanNYbmJGUFk Video In Action: https://drive.google.com/open?id=0B9eJ8PZ_4csMYmtYWnJJN1Rtc2M -- You received this bug notification because you are a member of DHIS 2 developers, which is subscribed to DHIS. https://bugs.launchpad.net/bugs/1614956 Title: Dataset Import/Export does not affect custom entry form Status in DHIS: New Bug description: A few things going on here: TL:DR 1. Dataset export does not contain the <dataEntryForms> tag as a child <metaData>. 2. Dataset uploads with <dataEntryForm> as a child of <dataSet> has no effect on the custom form 3. Dataset uploads with <dataEntryForms> as a child of <metaData> with matching entry under <dataSet> still has no effect on custom form Long Form: 1. I'm not sure where the intended location of the dataEntryForm custom HTML. If it is supposed to live as a child of <dataSet>, then all is fine. If it is supposed to live in <dataEntryForms> with a link to it in <dataSet> as I suspect, then exporting the dataSet should probably come with the <dataEntryForms> even if "Export With Dependencies" is _not_ checked. It is also strange to see the custom HTML twice when you do export with Dependencies. Which one is correct? It can also constrain a questionable connection if the custom form is very large, as the xml file is now doubled in size. 2. If I alter an exiting custom form in the <dataSet> section and try to upload the xml for it, it will not have any affect. See the video of this in action and the link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. 3. As above, if I alter an exiting custom form in the <dataEntryForms> section of the xml file, and try to upload the xml for it, it will not have any affect. See the video of this in action and the link to the xml file I'm using to do this on the play demo site. This behavior is the exact same for 2.23, where I first encountered it. Steps to Reporduce: 1. Log in as superuser 2. Download the following xml files, alter the name,shortname,code,uid and upload to playdemo 3. Make a an additional change to the custom form and upload to play demo, notice nothing actually changes. Without the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMcHlIalZTcUNGWkk With the Entry Form https://drive.google.com/open?id=0B9eJ8PZ_4csMRTNHanNYbmJGUFk Video In Action: https://drive.google.com/open?id=0B9eJ8PZ_4csMYmtYWnJJN1Rtc2M To manage notifications about this bug go to: https://bugs.launchpad.net/dhis2/+bug/1614956/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
