a month ago - edited a month ago
Aggregate/Aggregation: A collection of deduplicated related/relevant attributes.
Spreadsheet/Excel Tab: A single spreadsheet or tab included within the workbook/Excel File.
Workbook/Excel File: The entire workbook/Excel File containing all spreadsheets and tabs.
Taxonomy: System classification, specific to recipient (or Syndigo).
Category: Categorization specific to Taxonomy chosen.
Recipient: Receiving entity.
Requirement Set: Contains the receiving entity's required data model and associated rules (specific channel).
Public/Global Attribution: Attributes that may be shared for all recipient requirements to utilize.
Override Attributes: Overrides can be set for a specific recipient requirement channel to override the public value. Overrides are usually intentionally set to send different data to a specific recipient that is different than a public value. Recipient-specific override values are not shared across other recipient requirement sets.
Private Attribution: Custom attributes that are specific to a custom requirement set or a specific recipient requirement set that are not shared between recipient requirement sets.
Simple Attribute: An attribute that has only one value field.
Container Attribute: An attribute that contains multiple simple attributes and may have multiple attribute values.
Complex Attribute: An attribute that contains multiple simple and/or container attribute values. Complex Attributes are not re-importable.
When Importing or Exporting product content, users have the options to
The purpose of the aggregate export is to consolidate the number of spreadsheets the user needs to fill out when updating product data across multiple recipient requirement sets. With the addition of aggregate exports, the Import/Export flow has also been updated and simplified to better match one another to lessen user confusion/error. Once the user selects a specific export path, they will then follow the same path upon reimport.
The main change with the Import/Export modal was removing the ability to apply Recipient Specific Overrides (targeted attribute values) via the Attribute Spreadsheet Path. The ability to add Recipient Specific Overrides will now be its own path option, “Attribute Value Override Spreadsheet”.
Importable Spreadsheet Options (Item Selection Not Required):
Attribute Spreadsheet: User can follow this path to export a single recipient requirement set or select multiple recipient requirements to combine global attributes into one aggregate spreadsheet for attribute value population and reimport.
If aggregation (or multiple recipient requirement sets) are selected, the spreadsheet will export an aggregation of attributes included in selected requirement sets. Attributes will be exported in order of required, conditional, and remaining optional attributes to be listed alphabetical order, with the Company’s chosen Primary Unique Identifier always showing in Column A.
Attribute Value Override Spreadsheet: User can follow this path to export a single requirement set’s recipient override values only. Attribute Value Override Spreadsheet option is intended for Recipient Specific Overrides. Recipient Specific Override values are targeted to a specific recipient and do not flow over to other recipient requirement sets and are only intended to syndicate to recipient selected upon import.
Product URL Spreadsheet: User should follow this path if they are looking to export Product Pages (Site URLs) for Analytics & Reporting and Enhanced Content purposes.
Assets: User should follow this path to specify and export assets to a zip file or Asset URL spreadsheet.
ACES Application File Export: Automotive users should follow this path if they need to export their flattened ACES file.
(Recipient) Workflow Spreadsheet: Recipient users should follow this path to export items in a specific workflow step.
Non-Importable Spreadsheet Export Options (Item Selection Required):
Product Table: Download a snapshot of your Product Index Page table with current columns. Edit Product Index Page columns using “Manage Columns” button above the Action Bar:
Complex Attributes: Complex attribute workbook. Each complex container attribute will receive its own workbook. Complex container attributes are non-importable.
Sell Sheets: Generate a Sell Sheet for the selected product in the Product Index Page. Only one product can be selected for this option to become available.
GDSN Status: Download the current recipient specific GDSN Statuses of item(s) selected in the Product Index Page.
CIC Message: Download the most recent recipient specific GDSN feedback/CIC Message in .XML for item(s) selected in the Product Index Page.
Linked GLN Export: Download a report of GLNs registered/associated of item(s) selected in the Product Index Page….Download the linked recipients with GLN for selected products.
Recipient Specific Template: Exports to a recipient specific template when needing your data/assets in a pre-defined format.
Manual Publication Template (Specific to Healthcare): Exports a template to enable import of selected items and objective evidence files to create manual publication records for product data submissions performance outside the platform.
Importing the same values for different locales: Aggregate path can be followed, but please note that not all recipient requirement sets support all locales.
Sections are divided by Export Path followed in the first modal. Feedback exports also get their own section:
Each tile represents an Excel File. The tile shows recipient requirement set names, category, locale, identifiers, and number of products included in the Excel File.
Taxonomy: Multiple Categories: If All Categories in one Workbook was chosen in previous modal. This does not include Complex/Container attributes that may be included within chosen recipient requirement sets.
Taxonomy: Specific Category: If Separate Workbook for all Categories was chosen in previous modal each category will receive its own workbook. This does not include Complex/Container attributes that may be included within chosen recipient requirement sets.
No Category: Aggregate workbooks and single recipient requirement set export with no chosen taxonomy, or recipient requirement set may not have a taxonomy applied.
Complex/Container Attributes receive their own workbook due to multi-values included in Complex/Container attribute. Attribute Name, recipient requirement set name and category (if applicable) will be notated on the tile for clarification.
Attribute Spreadsheet: User can follow this path to import a single recipient requirement set spreadsheet or an aggregate (multiple recipient requirement sets) spreadsheet. Attribute Spreadsheet path will apply public attribute values for item attributes filled out in spreadsheet. Public attribute values will flow over to other recipient requirement sets if any attributes are shared across recipient requirement sets.
Attribute Value Override Spreadsheet: User can follow this path to import a single recipient requirement set’s attribute override values only. Attribute Value Override Spreadsheet option is intended for Recipient Specific Overrides. Recipient Specific Override values are targeted to a specific recipient and do not flow over to other recipient requirement sets and are only intended to syndicate to recipient selected upon import.
Product URL Spreadsheet: Use the URL spreadsheet to seamlessly re-import product URLs to your PIM.
ACES Application File: Automotive users should follow this path if they need to import their flattened ACES file.
Product Assets: Users should follow this path to import assets to their Asset Library. Asset URL spreadsheet import should utilize the Attribute Spreadsheet path. Enabled with the GDSN Feature Set.
Additional Import Options (Recommended Defaulted):
If an attribute has error: How should Syndigo handle attribute values that do not meet data quality rules?
If an important product has an existing match: If a product already exists (based on Unique ID) how should Syndigo handle the duplicate?
If an imported product does not have an existing match: If a products does not exist (based on Unique ID) how should Syndigo handle the new item?
If an uploaded product matches more than one existing product: If there is more than one duplicate record in the user’s Product Index, how should Syndigo handle duplicate matching?
Do you want to verify products on import?: Verifying a product is related to Custom Distributions and Ecatalog. Do you want Syndigo to push the newly imported product data to your Custom Distributions and Ecatalog?
If uploading a blank value: If you are importing blank/null values, should Syndigo blank out those values if there is a value already present, or just ignore the blank/null value?
The purpose of combining category spreadsheets for a single taxonomy into a single workbook was to consolidate the number of workbooks exported different categories under a single taxonomy. If the user is exporting category specific spreadsheets, an extra option will be provided upon export for the user to choose to either combine spreadsheets into a single workbook or export category sheets in separate workbooks, as it functioned previously.
Separate workbook for each category: This option will create a workbook for each individual category chosen. How Syndigo has handled category specific exports in the past. Export Example:
All categories in one workbook: This option will consolidate all categories into one workbook, allowing a single sheet/tab for each category included. Note: User will still receive separate workbooks for container and complex attributes. Export Example: