Skip to content

Anonymous

← Gearset

My feedback

5 results found

  1. Cleanup Layout Assignments

    8 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

    2 comments  ·  Help us improve Gearset » Comparisons and difference visualization  ·  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
    Anonymous supported this idea  · 

  2. Integrate with Agile Accelerator instead of just Jira

    27 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

    2 comments  ·  Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.)  ·  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
    Anonymous supported this idea  · 

  3. Allow serial deployment instead of parallel

    6 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

    1 comment  ·  Help us improve Gearset » Data deployment  ·  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
    Anonymous shared this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
    Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
    For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
    If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.

  4. Delete records from the target org during a data deployment

    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  ·  Help us improve Gearset » Data deployment  ·  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
    Anonymous supported this idea  · 

  5. Include validation rules and triggers of managed packages in 'Compare and deploy disabled rules'

    2 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

    1 comment  ·  Help us improve Gearset » Data deployment  ·  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
    Anonymous shared this idea  · 

Feedback and Knowledge Base

(thinking…)