Skip to content
← Turn your feedback into functionality

Settings and activity

3 results found

  1. Spike Smart Duration + Sequential Due Date Issue with Due Dates going to the past or going out of order

    13 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    New  ·  0 comments  ·  CMP (Content Marketing Platform)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Ariba Sattar supported this idea  · 

  2. VMI - Add optional fields for display on labels

    17 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Configured Commerce  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Ariba Sattar supported this idea  · 

  3. Attribute Value Character Limit Raise

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  3 comments  ·  Configured Commerce  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Ariba Sattar commented  · 

    As a CSM, I am submitting this enhancement request on behalf of Stellar Industrial and their systems integration partner, Apexon, who are integrating an external AD-based product data feed with Optimizely Commerce Connect.

    Stellar Industrial's AD system supports attribute values up to 500 characters, but Commerce Connect currently limits the attributeValue table to nvarchar(255). When their data feed refresh job runs, any attribute value exceeding 255 characters causes the job to throw an error, resulting in incomplete and inaccurate product data in their catalog.

    What we're trying to solve: Stellar Industrial needs their AD data feed refresh jobs to complete without errors, and for all product attribute values to be saved accurately in Commerce Connect regardless of length.

    Desired outcome: Increasing the column size to nvarchar(500) would align Commerce Connect with the capacity of their source AD system, allowing data feed jobs to run reliably and ensuring product attribute data is fully and accurately reflected in Stellar Industrial's catalog.

    This is currently a blocker for reliable product data synchronization and is impacting catalog accuracy at scale.

    Ariba Sattar supported this idea  ·