This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| 2000_concepts:0900_prod_feats:0600_export_import [2026/08/13 00:53] – ↷ Links adapted because of a move operation localdev | 2000_concepts:0900_prod_feats:0600_export_import [2026/08/13 07:20] (current) – external edit 127.0.0.1 |
|---|
| For options 3 and 4 above the best approach is to define your own import or export template that defines mapping between the columns in the data file format supported by an external package and attributes of the object in AwareIM. AwareIM includes a sophisticated mapping module that allows end users to define such templates. | For options 3 and 4 above the best approach is to define your own import or export template that defines mapping between the columns in the data file format supported by an external package and attributes of the object in AwareIM. AwareIM includes a sophisticated mapping module that allows end users to define such templates. |
| |
| {{page>docs:5000_videos:450_import_export_templates&noheader}} | {{page>:5000_videos:450_import_export_templates&noheader}} |
| |
| There are several options that control how export is performed: | There are several options that control how export is performed: |
| It is possible to indicate whether values of the [[ref:glossary:id_attribute|ID attribute]] will be written into the output file. If this option is switched on //**AwareIM**// writes out values of the ID attribute for each instance of the exported business object. When such a file is imported back into the system //**AwareIM**// detects that the data contains the ID attribute and tries to find the corresponding instance in its database. Then it uses the data in the record to //modify// the instance rather than to //add// a new one. Thus this option controls whether exported data will later be used to import the new data as in scenario 1 or modify the existing data as in scenario 2. | It is possible to indicate whether values of the [[ref:glossary:id_attribute|ID attribute]] will be written into the output file. If this option is switched on //**AwareIM**// writes out values of the ID attribute for each instance of the exported business object. When such a file is imported back into the system //**AwareIM**// detects that the data contains the ID attribute and tries to find the corresponding instance in its database. Then it uses the data in the record to //modify// the instance rather than to //add// a new one. Thus this option controls whether exported data will later be used to import the new data as in scenario 1 or modify the existing data as in scenario 2. |
| |
| <callout type="primary" icon="true" title="note"> It is possible to use a particular attribute, rather than ID attribute to indicate update operation. If you add ''*'' symbol before the name of the object and attribute in the header of the CSV file, //**AwareIM**// will use values of this attribute to find instances of business objects to modify (only one instance must be found for each value of the attribute). This may be useful when exchanging data with non-//**AwareIM**// systems that do not have the ID attribute.</callout> | <alert type="primary" icon="fa info-circle"> |
| | **note** |
| | |
| | It is possible to use a particular attribute, rather than ID attribute to indicate update operation. If you add ''*'' symbol before the name of the object and attribute in the header of the CSV file, //**AwareIM**// will use values of this attribute to find instances of business objects to modify (only one instance must be found for each value of the attribute). This may be useful when exchanging data with non-//**AwareIM**// systems that do not have the ID attribute.</alert> |
| |
| |
| |
| See also: | See also: |
| {{simplenavi>docs:2000_concepts:0900_prod_feats:0600_export_import}} | {{simplenavi>.:0600_export_import}} |
| |