sections in the article
This article provides a list of the features of the inriver Salesforce B2C Commerce Adapter.
Salesforce B2C Commerce is referred to as Salesforce and the Salesforce B2C Commerce Adapter is referred to as the Salesforce Adapter in this article.
About the adapter
Read about the Salesforce Adapter in this article.
Feature list
This is a 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 |
Comment |
|
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 storefronts supported by one inriver environment |
yes |
|
|
Delete entities in the integrating system |
yes |
|
|
|
|
|
|
Relations |
|
|
|
Product -> Item Links |
yes |
|
|
Custom LinkTypes (any) |
partly |
By setting up recommendations of different types in the mapping file and in Salesforce. |
|
Sort order on Links (Product -> Items) |
yes |
Index on the link type defines the order. Controlled via an extension setting (ORDER_VARIATIONLINKS) |
|
Sort order on Links for Resources |
yes |
Index on the link type defines the order. |
|
Sort order on links for ChannelNodes |
partly |
Not a specified sort order, but ordered in the XML according to channel structure. |
|
|
|
|
|
Concepts |
|
|
|
DisplayName |
yes |
Fields can be mapped to corresponding system fields in Salesforce. |
|
DisplayDescription |
yes |
Fields can be mapped to corresponding system fields in Salesforce. |
|
MainPicture |
no |
|
|
CVL:s handled as "lists" |
yes |
|
|
FieldSets |
no |
|
|
inriver Categories |
no |
|
|
Model Updates |
partly |
New fields must be manually added to mapping file. |
|
|
|
|
|
Resources |
|
|
|
Resources on Item |
yes |
|
|
Resources on Product |
yes |
|
|
Resources on ChannelNode |
no |
|
|
Resources on any Entity |
no |
|
|
Resources without file (URL) |
no |
Save the URLs on Product/Item instead and handle the re-link in the site implementation. |
|
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) |
yes |
|
|
Send only changed media files |
yes |
Uses file size to determine if the media file has been updated and needs to be sent across |
|
|
|
|
|
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 |
|
|
DataType CVL (LocaleString) |
yes |
|
|
DataType CVL (multi-value) |
yes |
|
|
Predefined EntityTypes, for instance "Look/Bundle" |
no |
|
|
Custom Entities (any) |
no |
|
|
Specification |
no |
|
|
Advanced Text Objects |
no |
|
|
MetaData on links (LinkEntity one/many fields) |
no |
|
|
MetaData on ChannelNodes |
yes |
|
|
SKU XML in PIM transformed to Items/Variants |
yes |
|
Comments
0 comments
Please sign in to leave a comment.