Informatica PIM. Export - Data types. Version: Date:

Transcription

1 Informatica PIM Export - Data types Version: Date: 12 July 29, 2014

2 Table of Contents Export data types 3 Where do I encounter export data types? 3 Which kind of export data types exist? 3 How can I use a data type programmatically? 4... as data type of a data provider parameter 4... as main data type of a data provider 4... as sub-data type of a data provider 5 Customizing possibilities 5 Repository 5 Provide a new data type representing a repository enumeration 5 Provide a new data type representing a repository sub-entity 6 Implement a new data type 7 Qualifying a data field: which variable matches? 7 Special export sub data types 12 File attachments of items, products, structure groups 12 Available fields 13 Data type filter 13 Load and prepare data 13 Determine the list of media assets to be exported 13 Get a listmodel for each of the sub entities 13 Merge the list models 13 Post-prepare the listmodel 13 Support of "language independent" document language 14 Examples 14 Example 1: Consistent data 14 Example 2: No documents 15 Example 3: No descriptions 15 Attributes and features of items and products 16 Attribute values and feature values of items and products 16

3 This article is still under construction What are export data types? Why do I need export data types? How can I add a new data type? This article applies to the Heiler Product Manager in versions 7.0 and above. Export data types Note: You can find a list of existing standard export data types. Where do I encounter export data types? (Main) Data type of data providers Sub-data types of data providers Data types for data provider parameters resp. export post step parameters Data types for variables qualify data fields configure data type filters specify export parameter values Which kind of export data types exist? Data types representing a repository root entity Data types representing a repository sub-entity Data types representing several repository sub-entities Data types representing a repository enumeration Special data types 3

4 How can I use a data type programmatically?... as data type of a data provider parameter Example: boolean parameter of a data provider ValueDescriptor updateassortmentparameter = new ValueDescriptor() { public DataType getdatatype() { return DataTypeFactory.getInstance().getDataType( DataTypeBoolean.IDENTIFIER ); } //... };... as main data type of a data provider Example: main data type of a data provider public class StructureDataProvider extends ReportListModelQueryDataProviderBaseImpl { public DataType getdatatype() { return DataTypeFactory.getInstance().getDataType( DataTypeStructure.IDENTIFIER ); } //... } 4

5 ... as sub-data type of a data provider Example: add a sub-data type to a data provider public class StructureDataProvider extends ReportListModelQueryDataProviderBaseImpl { public List getsubdatatypes() { List subdatatypes = new ArrayList(); //... DataTypeUtils.addSubDatatype( subdatatypes, DataTypeStructureAttributes.IDENTIFIER ); //... return subdatatypes; } //... } Customizing possibilities Repository Provide a new data type representing a repository enumeration If there's a (new) repository enumeration you want to provide as export variable data type you just have to add a new enum param with the "useforexportdatatype" key and the "true" value: Now you can use the new data type: 5

6 Provide a new data type representing a repository sub-entity If there's a (new) repository sub-entity you want to export as it is, you only have to set the export purpose of this sub-entity to "1". Now there's a new sub-data type, the data of this entity are ready to be exported: 6

7 Implement a new data type tbd Qualifying a data field: which variable matches? If you want to qualify an export data field you can specify a dedicated value, or - if the corresponding logical key represents a date or an enumeration and if there's an export data type representing this enumeration - you can use a variable. Example: There're two variables defined "Language" with data type "Language" representing the repository enumeration "Language" "Language_incl_langIndependent" with data type "Languages (Including language independent)" representing the repository enumeration "Languages (Including language independent)" 7

8 8

9 Adding the "Items.Short description" field requires qualification with a language. You can choose a language value directly, or you can use a variable that provides valid values for the corresponding logical key. The "Language" variable matches because it represents exactly the list of languages the logical key's enumeration defines. 9

10 10

11 Adding the "Items.Attribute value" field requires qualification with a language, too. Here, you can use a specific value or a variable that provides valid values for the corresponding logical key. Both - "Language" and "Language_incl_langIndependent" - variables match, because "Language_incl_langIndependent" variable represents exactly the list of languages the logical key's enumeration defines "Language" variable represents a sub-list of the allowed languages 11

12 Special export sub data types File attachments of items, products, structure groups Many export data sources provide a sub data type for file attachments. All these sub data types provide the same list of data fields, and use the same algorithm to retrieve data to be exported. 12

13 Available fields The file attachments data types provide all fields... that are enabled for export (export purpose is not 0) that are fields of MediaAsset, MediaAssetLang, MediaAssetDocument, MediaAssetDocumentAttributes repository entities. These fields don't have to be qualified. Data type filter You can use all logical keys of the MediaAsset sub entities as data type filters: language, quality, type. These data types provide an additional filter "Mandatory fields", that can prevent output of inconsistent data rows. Load and prepare data The following algorithm is used to create the file attachments list model: Determine the list of media assets to be exported The data providers list of items, products, or structure groups is used to get the mapped media assets. The resulting report of media assets is used by the next steps. Get a listmodel for each of the sub entities The requested data fields are splitted by its entities, a listmodel is retrieved for each sub entity: MediaAssetDocumentAttributes - if any fields are requested for this entity MediaAssetDocument - always MediaAssetLang - if any fields are requested for this entity MediaAsset - always Merge the list models The listmodels are merged in this order and with this rules: MediaAssetDocument and MediaAssetDocumentAttributes: merge by MediaAssetDocumentId with MediaAssetDocument as master, result: MediaAssetDocument MediaAssetDocument and MediaAssetLang: full merge by MediaAssetId and LanguageId, result: MediaAssetDocument MediaAsset and MediaAssetDocument: left outer merge by MediaAssetId with MediaAsset as master Post-prepare the listmodel Last step is to validate and sort the listmodel. 13

14 Support of "language independent" document language Often media asset documents are not language dependent. That's why the file attachment sub data types support a substitute language for documents, see substitute language. The merge algorithm of MediaAssetDocument and MediaAssetLang listmodels determines matching entries by MediaAssetId and LanguageId. If no suitable MediaAssetDocument entry is found for a MediaAssetLang entry, an entry with same MediaAssetId and LanguageId = "substitute language" is used instead. That means the media asset document entry of the substitute language is assigned to a media asset description if there's no document with description's language. TODO screen Examples The following export template is used for all examples: Example 1: Consistent data There're descriptions and documents for german and english language. 14

15 Example 2: No documents There're descriptions, but no documents. Example 3: No descriptions There're documents but no media asset descriptions. 15

16 Attributes and features of items and products TODO Attribute values and feature values of items and products TODO 16