Take the community feedback survey now.
AI OnAI Off
CommerceConnect not showing all SerializableCarts and orders in case you have a lot of Markets
Hi Roland,
You are right. the 512-character limit on MarketIds and 4000-character limit on Query are restrictive for B2B scenarios with many markets.
Short term:
Your fix of changing the stored procedure parameters to NVARCHAR(MAX) is correct and addresses the root cause.
The specific changes needed are:
-
In ecf_SerializableCart_Filter:
- Change @MarketIds NVARCHAR(512) to @MarketIds NVARCHAR(MAX)
Change @Query NVARCHAR(4000) to @Query NVARCHAR(MAX)
- Change @MarketIds NVARCHAR(512) to @MarketIds NVARCHAR(MAX)
-
In ecf_PurchaseOrder_Filter
- Apply the same parameter changes
Long-term Approach
Since you're concerned about future updates overwriting your changes, here are your options:
1. Report to Optimizely Support
Submit this as a bug report through Optimizely's support channels.
2. Version Control Your Database Changes
- Maintain SQL scripts with your modifications
- Document which stored procedures you've modified
- Create automated deployment scripts that can reapply your changes after Optimizely updates
I'd strongly recommend submitting this to Optimizely as a bug report or enhancement request, as this limitation affects scalability for legitimate B2B use cases. In the meantime, your NVARCHAR(MAX) solution is the correct technical fix.
Edited,
Aug 15, 2025 11:45
Thank you for your feedback Aniket! I have since reported the issue at Optimizely, see:
Aug 18, 2025 11:49
For our B2B use-case on CMS12/CommerceConnect14 we got quite some markets, every main customer (parent-organization) has it's own market, and per product-variant it's own prices.
While updating to CMS12/CommerceConnect14 we found some bugs when trying to load all SerializableCarts or Orders. While looking into the SP's used for loading these:-
We found out that the following fields are causing the issues:
By setting both (on multiple places) to NVARCHAR(MAX) all Carts and Orders do load.
I can understand we have quite a specific case with a lot of markets, but since this field is limited to 512 characters, this value is reached quite easily.
When you count with 8 chars for the market, and the comma (e.g.: 0005d129,0006f7d4,etc..) this is already reached with 57 markets.
Updating the SP's is not hard, but will be an issue when Optimizely updates these SP's in a future release.
Can this be looked into, and fixed by Optimizely?