sections in the article
This article provides a detailed list of the features of the Adobe Magento Commerce Adapter. For a high-level list of features, read this article.
Adobe Magento Commerce is referred to as Magento and the Adobe Magento Commerce Adapter is referred to as the Magento Adapter in this article.
About the adapter
Read about the Magento Adapter in this article.
Detailed feature list
This is a detailed list of what the adapter supports and some limitations. Use cases or features that are not listed should be considered as a "No", at least until you have tested and verified them yourself.
Note that a limitation to a feature doesn't mean that the integrating system doesn't have the possibility to support the feature.
|
Feature |
Yes/Partly/No |
Comments |
|
Misc |
||
|
Structure from Channel/ChannelNodes replicated |
Yes |
|
|
Same Entity at multiple locations in the channel |
Yes |
|
|
Same ChannelNode at multiple locations in the channel |
No |
ChannelNodes need to have unique IDs |
|
Multiple Channels publishing to the same integrating system |
Yes |
|
|
Multiple StoreViews supported by one inriver environment |
Yes |
|
|
Delete entities in the integrating system |
Partly |
Products are deactivated, not deleted. Categories are deleted. Deletions of attribute options are not supported. |
|
Same extension to multiple Magento instances |
No |
It’s 1 extension for 1 Magento instance |
|
Relations |
||
|
Product -> Item Links |
Yes |
|
|
Custom LinkTypes (any) |
Partly |
1:n are not supported |
|
Sort order on Links (Product -> Items) |
Yes |
|
|
Sort order on Links for Resources |
Yes |
|
|
Sort order on links for ChannelNodes |
No |
Categories will be in the PIM sort order at the initial load, when all categories are created, and not when updated. |
|
Concepts |
||
|
DisplayName/DisplayDescription |
Yes |
Part of the FieldType and Attribute mapping |
|
MainPicture |
Yes |
|
|
CVL Values handled as "Options" |
Yes |
Only in product |
|
FieldSets |
Yes |
|
|
FieldType Categories |
No |
|
|
Model Updates |
No |
New FieldTypes need to be created in Magento and then mapped in the extension setting |
|
Attribute groups on Categories |
No |
|
|
Extended attributes on Categories |
Yes |
|
|
Link Entities on Categories |
No |
|
|
Resources |
||
|
Resources on Item |
Yes |
|
|
Resources on Product |
Yes |
|
|
Resources on ChannelNode |
No |
|
|
Resources on any Entity |
No |
|
|
Resources without file (URL) |
Yes |
|
|
Use inriver Image Service to scale images |
Yes |
|
|
Same Resource on several Entities, only send once |
Yes |
|
|
MetaData on Resources |
No |
|
|
Multiple image configurations for resource |
Yes |
|
|
Non-image Resources (.pdf, .doc) |
No |
Not supported natively by Magento. |
|
Send only changed media files |
No |
Images are exported with their respective products |
|
Swatch as image |
Yes |
|
|
Types of Data |
||
|
DataType String |
Yes |
|
|
DataType LocaleString |
Yes |
|
|
DataType Boolean |
Yes |
|
|
DataType Int |
Yes |
|
|
DataType Double |
Yes |
|
|
DataType XML (handled as string) |
Yes |
|
|
DataType CVL (string) |
Yes |
CVL Keys in product & category export. |
|
DataType CVL (LocaleString) |
Yes |
|
|
DataType CVL (multi-value) |
Yes |
|
|
Predefined EntityTypes, for instance "Look/Bundle" |
Yes |
|
|
Custom Entities (any) |
Partly |
Except 1:n relations |
|
Specification |
Yes |
Not on categories & images |
|
Advanced Text Objects |
Yes |
|
|
MetaData on links (LinkEntity one/many fields) |
Partly |
For Bundle Products only |
|
MetaData on ChannelNodes |
Yes |
|
|
SKU JSON in PIM transformed to Items/Variants |
Yes |
|
|
Magento-Specific |
||
|
Magento 2 B2B and the Shared Catalog |
No |
|
|
Magento 2 Content Staging & Preview |
No |
|
|
Catalog Permissions |
No |
|
|
Tiered Pricing |
No |
|
|
Price & Inventory |
Partly |
Price can be mapped as an attribute |
Comments
0 comments
Please sign in to leave a comment.