Skip to content

Brother Dike

← Gearset

My feedback

1 result found

  1. Unable to import/export translations using .stf file using greaset

    5 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
    An error occurred while saving the comment
    Brother Dike commented  · 

    This would be awesome. We are rolling out our Salesforce implementation across 10+ languages, we are attempting to use a third party translation service which requires a properties file as input. While we can capture translations made through Translation Workbench we are not able to get such granular control on the Translation Workbench Export/Import for XML or STF (we use stf). The files export is not very clean. We get URLs, HTML tags, and duplicate values in the Keys. Which means we need to manually manipulate this export file before checking it into our version control repo used to interface with our third-party translation services.
    Being able to have Gearset allow us to create filters/compares for translation workbench import/export would save our team a ton of time each deployment.
    We looked into using metadata exports as an optional format to interface with our third-party translation provider but the translation file structures are different formats between picklists, objects, custom labels, and other metadata types. which causes difficulties when attempting to produce properties files(Key/value) pairs.

    Brother Dike supported this idea  · 

Feedback and Knowledge Base

(thinking…)