Upgrade iReports to 6.0 - Revision history

Alnaucler at 11:40, 7 July 2015

2015-07-07T11:40:06Z

← Older revision		Revision as of 13:40, 7 July 2015
Line 89:		Line 89:
	In case variables are defined and using fields that have been changed (e.g. SQL fields or fields whose name has changed), then they need to be adapted accordingly.		In case variables are defined and using fields that have been changed (e.g. SQL fields or fields whose name has changed), then they need to be adapted accordingly.

			==== Adapt labels====__NOEDITSECTION__
			Labels might need to be adapted too due to language or that terms have changed e.g. from Mine Action Area Type to Land Classification.
			[[Image:iReport fonts.png\|center]]
	=== Test and import into IMSMA ===__NOEDITSECTION__		=== Test and import into IMSMA ===__NOEDITSECTION__
	Once all those changes have been made, the report should be ready to run in V6. Finalise the upgrade by carrying out the following steps:		Once all those changes have been made, the report should be ready to run in V6. Finalise the upgrade by carrying out the following steps:

Alnaucler at 11:12, 7 July 2015

2015-07-07T11:12:51Z

← Older revision		Revision as of 13:12, 7 July 2015
Line 24:		Line 24:
	</div>		</div>
	\|}		\|}
	In order to upgrade the identified custom iReport templates, the ~~following~~ steps need to be performed:		In order to upgrade the identified custom iReport templates, the steps below need to be performed.

	==Steps for upgrading iReport templates ==__NOEDITSECTION__		==Steps for upgrading iReport templates ==__NOEDITSECTION__
Line 32:		Line 32:
	=== Get the JRXML files of the iReport templates ===__NOEDITSECTION__		=== Get the JRXML files of the iReport templates ===__NOEDITSECTION__
	The templates that shall be upgraded need to be opened with iReport. If the .jrml files were '''not''' included in the backup then you may extract them from the database with the following steps are required:		The templates that shall be upgraded need to be opened with iReport. If the .jrml files were '''not''' included in the backup then you may extract them from the database with the following steps are required:
	* Use pgAdmin3 or Navicat to connect to the imsma database		<ol>
	* Open the table called ''reporttemplate'' or issue the following query:		<li> Use pgAdmin3 or Navicat to connect to the imsma database.</li>
			<li> Open the table called ''reporttemplate'' or issue the following query:
	<pre>		<pre>
	SELECT * FROM reporttemplate ORDER BY name		SELECT * FROM reporttemplate ORDER BY name
	</pre>		</pre></li>
	* Navigate to the right row (corresponding to the report template name you are looking for) and copy the content of the column called '''jrxml'''. The content of this column starts with <?xml version=1.0		<li> Navigate to the right row (corresponding to the report template name you are looking for) and copy the content of the column called '''jrxml'''. The content of this column starts with <?xml version=1.0</li>
	* Paste the text into e.g. Notepad++ and ensure that there are no double quotes (") at the very beginning and end of the text (this happens when you copy-paste from pgAdmin3 - in this case delete the double quotes)		<li> Paste the text into e.g. Notepad++ and ensure that there are no double quotes (") at the very beginning and end of the text (this happens when you copy-paste from pgAdmin3 - in this case delete the double quotes).</li>
	* Save the document as <name>.jrxml (not .txt, the extension needs to be .jrxml) in ''C:\IMSMAng\iReport\Templates\Report Templates''.		<li> Save the document as <name>.jrxml (not .txt, the extension needs to be .jrxml) in ''C:\IMSMAng\iReport\Templates\Report Templates''.</li>
	* Open iReport ([[IReport does not start]])		<li> Open iReport ([[IReport does not start]]).</li>
	* Open the file saved before (<name>.jrxml) in iReport		<li> Open the file saved before (<name>.jrxml) in iReport.</li>
			</ol>
	=== Adapt the iReport templates ===__NOEDITSECTION__		=== Adapt the iReport templates ===__NOEDITSECTION__
	The following adaptations can now be made to the iReport template:		The following adaptations can now be made to the iReport template:
	==== Adapt the general report definition ====__NOEDITSECTION__		==== Adapt the general report definition ====__NOEDITSECTION__
	* Switch to the XML view of the report:		<ol>
	[[File:IReport XML View.png\|center]]		<li> Switch to the XML view of the report:
	* Delete all the lines that start with '''<import value='''		[[File:IReport XML View.png\|center]]</li>
	* Change '''language="java"''' to '''language="groovy"''' in the attribute list of the tag '''jasperReport''' at the top of the document (just search for language to find the place)		<li> Delete all the lines that start with '''<import value='''</li>
	* Search for the tag '''queryString''' and ensure that the attribute '''language''' is set to ImsmaQuerylike this:		<li> Change '''language="java"''' to '''language="groovy"''' in the attribute list of the tag '''jasperReport''' at the top of the document (just search for language to find the place).</li>
			<li> Search for the tag '''queryString''' and ensure that the attribute '''language''' is set to ImsmaQuerylike this:
	<pre>		<pre>
	<queryString language="ImsmaQuery">		<queryString language="ImsmaQuery">
	</pre>		</pre></li>
			</ol>
	==== Adapt Data Source ====__NOEDITSECTION__		==== Adapt Data Source ====__NOEDITSECTION__
	Choose the right data source. If you are not sure, look in the table in column ''Type''.		Choose the right data source. If you are not sure, look in the table in column ''Type''.

	==== Adapt GUID fields ====__NOEDITSECTION__		==== Adapt GUID fields ====__NOEDITSECTION__
	* Switch back to the Designer view of the report.		<ol>
	* Expand the Fields in the Report Inspector and look for the field '''guid'''		<li> Switch back to the Designer view of the report.
	[[File:iReport_guid_field.png\|center]]		<li> Expand the Fields in the Report Inspector and look for the field '''guid'''
	* If a guid field exists, select it and, in the '''Properties''' window on the right-hand side, click on the dots next to '''Properties'''		[[File:iReport_guid_field.png\|center]]</li>
	[[File:iReport_guid_properties.png\|center]]		<li> If a guid field exists, select it and, in the '''Properties''' window on the right-hand side, click on the dots next to '''Properties'''
	* In the next dialog window, click '''Add'''.		[[File:iReport_guid_properties.png\|center]]</li>
	* In the add/modify property window, add the following:		<li> In the next dialog window, click '''Add'''.</li>
	** Property name: '''imsma.type'''		<li> In the add/modify property window, add the following:
	** Property value: object name, e.g. '''HAZARD''' or '''HAZARD_REDUCTION''', etc. depending on the object (data source) that the report is defined on		:* Property name: '''imsma.type'''
			:* Property value: object name, e.g. '''HAZARD''' or '''HAZARD_REDUCTION''', etc. depending on the object (data source) that the report is defined on
	[[File:iReport_guid_properties_add.png\|center]]		[[File:iReport_guid_properties_add.png\|center]]
	* Click OK twice to save and exit.		<li> Click OK twice to save and exit.</li>
			</ol>
	==== Adapt SQL fields ====__NOEDITSECTION__		==== Adapt SQL fields ====__NOEDITSECTION__
	SQL fields, if used in a report, need to be adapted in two ways:		SQL fields, if used in a report, need to be adapted in two ways:
	* The need to be renamed from ''com.fgm.imsma.ext.report.xxx'' to e.g. ''HazardSQLField''. In order to be sure about the spelling, an empty report containing all fields of a data source can be created, which then allows to copy-paste fields from this empty report into the ones that is being upgraded.		<ol>
	* The SQL query needs to be adapted to the PostgreSQL syntax. Check [[http://mwiki.gichd.org/IM/Difference_MySQL_PostGreSQL#Most_common_changes_in_queries_and_views_from_MySQL_to_PostgreSQL\|this page]] for more details.		<li> The need to be renamed from ''com.fgm.imsma.ext.report.xxx'' to e.g. ''HazardSQLField''. In order to be sure about the spelling, an empty report containing all fields of a data source can be created, which then allows to copy-paste fields from this empty report into the ones that is being upgraded.</li>
			<li> The SQL query needs to be adapted to the PostgreSQL syntax. Check [[http://mwiki.gichd.org/IM/Difference_MySQL_PostGreSQL#Most_common_changes_in_queries_and_views_from_MySQL_to_PostgreSQL \|this page]] for more details.</li>
			</ol>
	==== Adapt field names ====__NOEDITSECTION__		==== Adapt field names ====__NOEDITSECTION__
	Some IMSMA field names have changed from 5.08.04 to V6. The following error message (when trying to preview the report) can be an indication for that:		Some IMSMA field names have changed from 5.08.04 to V6. The following error message (when trying to preview the report) can be an indication for that:
Line 78:		Line 85:
	However, check first that the right data source is used indeed.		However, check first that the right data source is used indeed.
	There is no exhaustive list of all changes yet, but please get in touch with VIE in case of doubt.		There is no exhaustive list of all changes yet, but please get in touch with VIE in case of doubt.

	==== Adapt variables ====__NOEDITSECTION__		==== Adapt variables ====__NOEDITSECTION__
	In case variables are defined and using fields that have been changed (e.g. SQL fields or fields whose name has changed), then they need to be adapted accordingly.		In case variables are defined and using fields that have been changed (e.g. SQL fields or fields whose name has changed), then they need to be adapted accordingly.

	=== Test and import into IMSMA ===__NOEDITSECTION__		=== Test and import into IMSMA ===__NOEDITSECTION__
	Once all those changes have been made, the report should be ready to run in V6. Finalise the upgrade by carrying out the following steps:		Once all those changes have been made, the report should be ready to run in V6. Finalise the upgrade by carrying out the following steps:
	* Compile the report in iReport {{Note\|If there are errors, they are most likely not related to the upgrade.}}		<ol>
	* Preview the report in iReport {{Note\|If there are errors, they are most likely not related to the upgrade.}}		<li> Compile the report in iReport {{Note\|If there are errors, they are most likely not related to the upgrade.}}</li>
	* Import the iReport template into IMSMA		<li> Preview the report in iReport {{Note\|If there are errors, they are most likely not related to the upgrade.}}</li>
	* Adapt the report definition in IMSMA		<li> Import the iReport template into IMSMA.</li>
	* Test the report by running it in IMSMA		<li> Adapt the report definition in IMSMA.</li>
	* Delete the old reports and report templates in IMSMA		<li> Test the report by running it in IMSMA.</li>
			<li> Delete the old reports and report templates in IMSMA.</li>
			</ol>
	{{NavBox Upgrade}}		{{NavBox Upgrade}}

	[[Category:NoPublic]]		[[Category:NoPublic]]

Alnaucler at 06:40, 7 July 2015

2015-07-07T06:40:47Z

Alnaucler at 17:29, 6 July 2015

2015-07-06T17:29:03Z

← Older revision		Revision as of 19:29, 6 July 2015
Line 40:		Line 40:
	* Paste the text into e.g. Notepad++ and ensure that there are no double quotes (") at the very beginning and end of the text (this happens when you copy-paste from pgAdmin3 - in this case delete the double quotes)		* Paste the text into e.g. Notepad++ and ensure that there are no double quotes (") at the very beginning and end of the text (this happens when you copy-paste from pgAdmin3 - in this case delete the double quotes)
	* Save the document as <name>.jrxml (not .txt, the extension needs to be .jrxml) in ''C:\IMSMAng\iReport\Templates\Report Templates''.		* Save the document as <name>.jrxml (not .txt, the extension needs to be .jrxml) in ''C:\IMSMAng\iReport\Templates\Report Templates''.
	* Open iReport ([[~~Problem starting iReport~~]])		* Open iReport ([[IReport does not start]])
	* Open the file saved before (<name>.jrxml) in iReport		* Open the file saved before (<name>.jrxml) in iReport

Line 54:		Line 54:
	<queryString language="ImsmaQuery">		<queryString language="ImsmaQuery">
	</pre>		</pre>

			==== Adapt Data Source ====__NOEDITSECTION__
			Choose the right data source. If you are not sure, look in the table in column ''Type''.
	==== Adapt GUID fields ====__NOEDITSECTION__		==== Adapt GUID fields ====__NOEDITSECTION__
	* Switch back to the Designer view of the report		* Switch back to the Designer view of the report

Alnaucler at 17:06, 6 July 2015

2015-07-06T17:06:08Z

← Older revision		Revision as of 19:06, 6 July 2015
Line 31:		Line 31:

	=== Get the JRXML files of the iReport templates ===__NOEDITSECTION__		=== Get the JRXML files of the iReport templates ===__NOEDITSECTION__
	The templates that shall be upgraded need to be opened with iReport. ~~To be able to do so,~~ the ~~related~~ .~~jrxml~~ files ~~need to be extracted~~ from the database~~. The~~ following steps are required:		The templates that shall be upgraded need to be opened with iReport. If the .jrml files were '''not''' included in the backup then you may extract them from the database with the following steps are required:
	* Use pgAdmin3 or Navicat to connect to the imsma database		* Use pgAdmin3 or Navicat to connect to the imsma database
	* Open the table called '''reporttemplate''' or issue the following query:		* Open the table called '''reporttemplate''' or issue the following query:
Line 39:		Line 39:
	* Navigate to the right row (corresponding to the report template name you are looking for) and copy the content of the column called '''jrxml'''. The content of this column starts with <?xml version=1.0		* Navigate to the right row (corresponding to the report template name you are looking for) and copy the content of the column called '''jrxml'''. The content of this column starts with <?xml version=1.0
	* Paste the text into e.g. Notepad++ and ensure that there are no double quotes (") at the very beginning and end of the text (this happens when you copy-paste from pgAdmin3 - in this case delete the double quotes)		* Paste the text into e.g. Notepad++ and ensure that there are no double quotes (") at the very beginning and end of the text (this happens when you copy-paste from pgAdmin3 - in this case delete the double quotes)
	* Save the document as <name>.jrxml (not .txt, the extension needs to be .jrxml)		* Save the document as <name>.jrxml (not .txt, the extension needs to be .jrxml) in ''C:\IMSMAng\iReport\Templates\Report Templates''.
	* Open iReport		* Open iReport ([[Problem starting iReport]])
	* Open the file saved before (<name>.jrxml) in iReport		* Open the file saved before (<name>.jrxml) in iReport

Alnaucler at 16:54, 6 July 2015

2015-07-06T16:54:22Z

← Older revision		Revision as of 18:54, 6 July 2015
Line 3:		Line 3:
	When upgrading IMSMA from 5.08.04 to V6, the iReport templates, if there are any, need to be upgraded separately - this is not included in any automatic process. Custom report templates as well as created reports will be transferred to V6, but they will not be working/usable. In order to make them usable, follow the steps as described on this page.		When upgrading IMSMA from 5.08.04 to V6, the iReport templates, if there are any, need to be upgraded separately - this is not included in any automatic process. Custom report templates as well as created reports will be transferred to V6, but they will not be working/usable. In order to make them usable, follow the steps as described on this page.

	~~IMSMA V6~~ comes with 35 inspirational iReport templates. Therefore, if there are more than 35 in the '''Report Template Manager''', it means that custom ones have been created by the country, and need to be investigated one by one. The names of all the inspirational iReport templates start with either:		{{IMSMANG}} version 6.0 comes with 35 inspirational iReport templates. Therefore, if there are more than 35 in the '''Report Template Manager''' in the Customisation menu, it means that custom ones have been created by the country, and need to be investigated one by one. The names of all the inspirational iReport templates start with either:
	* List - xxx, e.g. List - Land		* List - xxx, e.g. List - Land
	* Geospatial - xx, e.g. Geospatial - Activity		* Geospatial - xx, e.g. Geospatial - Activity
	* Statistics - xx, e.g. Statistics - Land with Ordnance Details		* Statistics - xx, e.g. Statistics - Land with Ordnance Details

	[[File:Report_Template_Manager_custom_iReports.png\|center\|700px]]		In {{IMSMANG}} version 6.0 there are 3 Report definitions. Therefore, if there are more than 3 in the '''Report List Window''' in the Report menu, it means that the custom Report definitions have been done by the country. After the iReports templates themselves have been upgraded then the templates have to be tested with their Saved Searches.
			{\|
			\|- valign="top"
			\|
			{\|
			\|-
			\| [[File:Report_Template_Manager_custom_iReports.png\|center\|700px]]
			<div align="center">
			'' Customisation menu - Report Template Manager''
			</div>
			\|
			\| [[File:Report List Window.png\|center\|700px]]
			<div align="center">
			'' Report menu - Report List Window ''
			</div>
			\|}
	In order to upgrade the identified custom iReport templates, the following steps need to be performed:		In order to upgrade the identified custom iReport templates, the following steps need to be performed:

Evinek at 09:34, 2 July 2015

2015-07-02T09:34:28Z

← Older revision		Revision as of 11:34, 2 July 2015
Line 58:		Line 58:
	==== Adapt field names ====__NOEDITSECTION__		==== Adapt field names ====__NOEDITSECTION__
	Some IMSMA field names have changed from 5.08.04 to V6. The following error message (when trying to preview the report) can be an indication for that:		Some IMSMA field names have changed from 5.08.04 to V6. The following error message (when trying to preview the report) can be an indication for that:
	[[File:~~iReport_error_message~~.png\|center]]		[[File:Report_error_message.png\|center]]
	However, check first that the right data source is used indeed.		However, check first that the right data source is used indeed.
	There is no exhaustive list of all changes yet, but please get in touch with VIE in case of doubt.		There is no exhaustive list of all changes yet, but please get in touch with VIE in case of doubt.

Evinek at 16:09, 1 July 2015

2015-07-01T16:09:13Z

← Older revision		Revision as of 18:09, 1 July 2015
Line 61:		Line 61:
	However, check first that the right data source is used indeed.		However, check first that the right data source is used indeed.
	There is no exhaustive list of all changes yet, but please get in touch with VIE in case of doubt.		There is no exhaustive list of all changes yet, but please get in touch with VIE in case of doubt.
			==== Adapt variables ====__NOEDITSECTION__
			In case variables are defined and using fields that have been changed (e.g. SQL fields or fields whose name has changed), then they need to be adapted accordingly.
	=== Test and import into IMSMA ===__NOEDITSECTION__		=== Test and import into IMSMA ===__NOEDITSECTION__
	Once all those changes have been made, the report should be ready to run in V6. Finalise the upgrade by carrying out the following steps:		Once all those changes have been made, the report should be ready to run in V6. Finalise the upgrade by carrying out the following steps:

Evinek at 16:03, 1 July 2015

2015-07-01T16:03:24Z

← Older revision		Revision as of 18:03, 1 July 2015
Line 1:		Line 1:
	~~{{Under construction\|This page is under construction}}~~
	{{TOC right}}		{{TOC right}}
	== Introduction ==__NOEDITSECTION__		== Introduction ==__NOEDITSECTION__

Evinek at 16:02, 1 July 2015

2015-07-01T16:02:58Z

← Older revision		Revision as of 18:02, 1 July 2015
Line 54:		Line 54:
	* Click OK twice to save and exit		* Click OK twice to save and exit
	==== Adapt SQL fields ====__NOEDITSECTION__		==== Adapt SQL fields ====__NOEDITSECTION__
			SQL fields, if used in a report, need to be adapted in two ways:
			* The need to be renamed from '''com.fgm.imsma.ext.report.xxx'''to e.g. '''HazardSQLField'''. In order to be sure about the spelling, an empty report containing all fields of a data source can be created, which then allows to copy-paste fields from this empty report into the ones that is being upgraded.
			* The SQL query needs to be adapted to the PostgreSQL syntax. Check [[http://mwiki.gichd.org/IM/Difference_MySQL_PostGreSQL#Most_common_changes_in_queries_and_views_from_MySQL_to_PostgreSQL\|this page]] for more details.
			==== Adapt field names ====__NOEDITSECTION__
			Some IMSMA field names have changed from 5.08.04 to V6. The following error message (when trying to preview the report) can be an indication for that:
			[[File:iReport_error_message.png\|center]]
			However, check first that the right data source is used indeed.
			There is no exhaustive list of all changes yet, but please get in touch with VIE in case of doubt.
	=== Test and import into IMSMA ===__NOEDITSECTION__		=== Test and import into IMSMA ===__NOEDITSECTION__
			Once all those changes have been made, the report should be ready to run in V6. Finalise the upgrade by carrying out the following steps:
			* Compile the report in iReport {{Note\|If there are errors, they are most likely not related to the upgrade.}}
			* Preview the report in iReport {{Note\|If there are errors, they are most likely not related to the upgrade.}}
			* Import the iReport template into IMSMA
			* Adapt the report definition in IMSMA
			* Test the report by running it in IMSMA
			* Delete the old reports and report templates in IMSMA
	{{NavBox Upgrade}}		{{NavBox Upgrade}}

	[[Category:NoPublic]]		[[Category:NoPublic]]

← Older revision		Revision as of 08:40, 7 July 2015
Line 3:		Line 3:
	When upgrading IMSMA from 5.08.04 to V6, the iReport templates, if there are any, need to be upgraded separately - this is not included in any automatic process. Custom report templates as well as created reports will be transferred to V6, but they will not be working/usable. In order to make them usable, follow the steps as described on this page.		When upgrading IMSMA from 5.08.04 to V6, the iReport templates, if there are any, need to be upgraded separately - this is not included in any automatic process. Custom report templates as well as created reports will be transferred to V6, but they will not be working/usable. In order to make them usable, follow the steps as described on this page.

	{{IMSMANG}} version 6.0 comes with 35 inspirational iReport templates. Therefore, if there are more than 35 in the '''Report Template Manager''' in the Customisation menu, it means that custom ones have been created by the country, and need to be investigated one by one. The names of all the inspirational iReport templates start with either:		{{IMSMANG}} version 6.0 comes with 35 inspirational iReport templates. Therefore, if there are more than 35 in the ''Report Template Manager'' in the Customisation menu, it means that custom ones have been created by the country, and need to be investigated one by one. The names of all the inspirational iReport templates start with either:
	* List - xxx, e.g. List - Land		* List - xxx, e.g. List - Land
	* Geospatial - xx, e.g. Geospatial - Activity		* Geospatial - xx, e.g. Geospatial - Activity
	* Statistics - xx, e.g. Statistics - Land with Ordnance Details		* Statistics - xx, e.g. Statistics - Land with Ordnance Details

	In {{IMSMANG}} version 6.0 there are 3 Report definitions. Therefore, if there are more than 3 in the '''Report List Window''' in the Report menu, it means that the custom Report definitions have been done by the country. After the iReports templates themselves have been upgraded then the templates have to be tested with their Saved Searches.		In {{IMSMANG}} version 6.0 there are 3 Report definitions. Therefore, if there are more than 3 in the ''Report List Window'' in the Report menu, it means that the custom Report definitions have been done by the country. After the iReports templates themselves have been upgraded then the templates have to be tested with their Saved Searches.
	{\|		{\|
	\|- valign="top"		\|- valign="top"
Line 33:		Line 33:
	The templates that shall be upgraded need to be opened with iReport. If the .jrml files were '''not''' included in the backup then you may extract them from the database with the following steps are required:		The templates that shall be upgraded need to be opened with iReport. If the .jrml files were '''not''' included in the backup then you may extract them from the database with the following steps are required:
	* Use pgAdmin3 or Navicat to connect to the imsma database		* Use pgAdmin3 or Navicat to connect to the imsma database
	* Open the table called '''reporttemplate''' or issue the following query:		* Open the table called ''reporttemplate'' or issue the following query:
	<pre>		<pre>
	SELECT * FROM reporttemplate ORDER BY name		SELECT * FROM reporttemplate ORDER BY name
Line 58:		Line 58:
	Choose the right data source. If you are not sure, look in the table in column ''Type''.		Choose the right data source. If you are not sure, look in the table in column ''Type''.
	==== Adapt GUID fields ====__NOEDITSECTION__		==== Adapt GUID fields ====__NOEDITSECTION__
	* Switch back to the Designer view of the report		* Switch back to the Designer view of the report.
	* Expand the Fields in the Report Inspector and look for the field '''guid'''		* Expand the Fields in the Report Inspector and look for the field '''guid'''
	[[File:iReport_guid_field.png\|center]]		[[File:iReport_guid_field.png\|center]]
	* If a guid field exists, select it and, in the '''Properties''' window on the right-hand side, click on the dots next to '''Properties'''		* If a guid field exists, select it and, in the '''Properties''' window on the right-hand side, click on the dots next to '''Properties'''
	[[File:iReport_guid_properties.png\|center]]		[[File:iReport_guid_properties.png\|center]]
	* In the next dialog window, click '''Add'''		* In the next dialog window, click '''Add'''.
	* In the add/modify property window, add the following:		* In the add/modify property window, add the following:
	** Property name: '''imsma.type'''		** Property name: '''imsma.type'''
	** Property value: object name, e.g. '''HAZARD''' or '''HAZARD_REDUCTION''', etc. depending on the object (data source) that the report is defined on		** Property value: object name, e.g. '''HAZARD''' or '''HAZARD_REDUCTION''', etc. depending on the object (data source) that the report is defined on
	[[File:iReport_guid_properties_add.png\|center]]		[[File:iReport_guid_properties_add.png\|center]]
	* Click OK twice to save and exit		* Click OK twice to save and exit.
	==== Adapt SQL fields ====__NOEDITSECTION__		==== Adapt SQL fields ====__NOEDITSECTION__
	SQL fields, if used in a report, need to be adapted in two ways:		SQL fields, if used in a report, need to be adapted in two ways:
	* The need to be renamed from '''com.fgm.imsma.ext.report.xxx'''to e.g. '''HazardSQLField'''. In order to be sure about the spelling, an empty report containing all fields of a data source can be created, which then allows to copy-paste fields from this empty report into the ones that is being upgraded.		* The need to be renamed from ''com.fgm.imsma.ext.report.xxx'' to e.g. ''HazardSQLField''. In order to be sure about the spelling, an empty report containing all fields of a data source can be created, which then allows to copy-paste fields from this empty report into the ones that is being upgraded.
	* The SQL query needs to be adapted to the PostgreSQL syntax. Check [[http://mwiki.gichd.org/IM/Difference_MySQL_PostGreSQL#Most_common_changes_in_queries_and_views_from_MySQL_to_PostgreSQL\|this page]] for more details.		* The SQL query needs to be adapted to the PostgreSQL syntax. Check [[http://mwiki.gichd.org/IM/Difference_MySQL_PostGreSQL#Most_common_changes_in_queries_and_views_from_MySQL_to_PostgreSQL\|this page]] for more details.
	==== Adapt field names ====__NOEDITSECTION__		==== Adapt field names ====__NOEDITSECTION__