sections in the article
This article provides a list of the features of the inriver Salesforce B2B Commerce Adapter.
Salesforce B2B Commerce is referred to as Salesforce and the Salesforce B2B 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 |
yes |
|
|
Delete entities in the integrating system |
yes |
Configurable |
|
|
|
|
|
Relations |
|
|
|
Product -> Item Links |
yes |
|
|
Custom LinkTypes (any) |
no |
Through product-product relations. |
|
Sort order on Links (Product -> Items) |
yes |
Index on the LinkType defines the order. |
|
Sort order on Links for Resources |
yes |
Index on the LinkType defines the order. |
|
Sort order on links for ChannelNodes |
yes |
Index on the LinkType defines the order. |
|
|
|
|
|
Concepts |
|
|
|
DisplayName |
no |
|
|
DisplayDescription |
no |
|
|
MainPicture |
yes |
Main image in Salesforce will be the first sorted Resource in inriver. |
|
CVL:s handled as "lists" |
no |
|
|
FieldSets |
no |
|
|
Categories |
no |
|
|
Model Updates |
no |
|
| Channel Filters | yes |
|
|
|
||
|
Resources |
|
|
|
Resources on Item |
yes |
|
|
Resources on Product |
yes |
|
|
Resources on ChannelNode |
no |
|
|
Resources on any Entity |
no |
|
|
Resources without file (URI) |
yes |
Stored as FieldType on the Resource EntityType. |
|
Use inriver Image Service to scale images |
yes |
If stored inside inriver. |
|
Same Resource on several Entities, only send once |
yes |
|
|
MetaData on Resources |
no |
|
|
Multiple image configurations for Resource |
yes |
As per Salesforce standard. |
|
Non-image Resources (.pdf, .doc) |
no |
On roadmap for future release. |
|
|
|
|
|
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 handled but CVL lists not transferred. |
|
DataType CVL (LocaleString) |
yes |
DataType handled but CVL lists not transferred. |
|
DataType CVL (multi-value) |
yes |
DataType handled but CVL lists not transferred. |
|
Predefined EntityTypes for Bundles |
in later version |
Bundles, Kits |
|
Custom Entities (any) |
yes |
Managed by the integration framework. |
|
Specification |
partially |
inriver FieldTypes mapped to Salesforce CC_ProductSpecs. |
|
MetaData on links (LinkEntity one/many fields) |
no |
Standard Salesforce fields as part of Bundles version. |
|
MetaData on ChannelNodes |
no |
|
|
Structured SKU data Items/Variants |
yes |
Managed by the integration framework. |
| Execution | ||
| Scheduling | yes | Interval and time of day as per inriver-recommended standards. |
| Delta functionality | yes |
Controlled through delta date fields on the TargetExporter Entity and the relevant Main EntityTypes. Read more about the TargetExporter EntityType and the delta FieldTypes in this article. |
| Batch processing | yes | From an integration framework perspective as well as Salesforce stability measures. |
Comments
0 comments
Please sign in to leave a comment.