Skip to main content
Nintex Community Menu Bar
Solved

Excel as Middleware to do Language translations

  • October 10, 2019
  • 5 replies
  • 56 views
markoulakis

Hi everyone!

My SFDC BA is convinced we can use excel as middleware to perform language translations so I am trying to set that up now.  Ideally, the Addendum needs to be in the language the country uses (ie; US needs English and Spanish).  I have an excel file right now with 1 tab containing the Addendum in Spanish and a second tab in French.  I'm setting the table ranges per videos but I don't think its going to work as I don't understand how I can specify which tab I need to call on when running the package.  Has anyone had to do anything similar with language translations?  WE have to use over 20 different languages globally so I am looking for the easiest method to accomlish.  If excel as middleware is not best method, I am open to suggestions.

 

Thanks all!

Marie

Best answer by leighburke

Hi Marie,

 

Currently tables aren't supported inside of a component group, so if you can get away without a table that would be the easiest. You could use conditional text to hide or show the different tables, you can copy paste whole tables inside of conditional text(https://help.nintex.com/en-us/docgen/docservices/docgen-sfdc/Services/templates/ConditionalTextWord.htm). The other option would be having multiple templates that come in conditionally, instead of using component groups(https://help.nintex.com/en-us/docgen/#docgen-sfdc/Services/manageDDP/FileOptionsDynamic.htm).

 

 

    5 replies

    L
    Nintex Employee
    Forum|alt.badge.img+14
    • leighburkeNintex Employee
    • Nintex Employee
    • October 10, 2019

    Hi Marie,

     

    Does it actually need to translate or are just trying to send out content based on language? You could potentially use Component Group's(https://help.nintex.com/en-US/docgen/docservices/#docgen-sfdc/Services/manageDDP/t_componentLibrary.htm%3FTocPath%3DUse%2520advanced%2520techniques|Component%2520Library|_____0), to conditionally build out your addendum document. 

    markoulakis
    • markoulakis
    • Author
    • October 11, 2019

    Hi Leigh, 

     

    More so to send out specific content based on the language needed.  I was thinking about the Component Group too.  I will definintely look into going that route aas I don't think excel as middlweware really is the best option.

     

    Thanks!

    Marie

    markoulakis
    • markoulakis
    • Author
    • October 11, 2019

    Hi again Leigh!

    Trying to setup the Component Group.  My document contains a table and I'd like to be able to include that table in the component group I am creating.  Am I missing something?  I'm not able to see how to be able to format or add in a table in the editor. It's in the table where I need to add in my field tags.  Is it just better to have the tect and forego the table itself?  I'd rather not but if there is a limitation, then it would have to do.

     

    Thanks,

    Marie

    1 Attachments
    L
    Nintex Employee
    Forum|alt.badge.img+14
    • leighburkeNintex Employee
    • Nintex Employee
    • Answer
    • October 14, 2019

    Hi Marie,

     

    Currently tables aren't supported inside of a component group, so if you can get away without a table that would be the easiest. You could use conditional text to hide or show the different tables, you can copy paste whole tables inside of conditional text(https://help.nintex.com/en-us/docgen/docservices/docgen-sfdc/Services/templates/ConditionalTextWord.htm). The other option would be having multiple templates that come in conditionally, instead of using component groups(https://help.nintex.com/en-us/docgen/#docgen-sfdc/Services/manageDDP/FileOptionsDynamic.htm).

     

     

    markoulakis
    • markoulakis
    • Author
    • October 15, 2019
    Thanks, Leigh! I will try the conditional text route.
    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsCookie SettingsAccessibility statement