Add Language Localization to a Form

Office 365 #SharePoint multi language custom form | Valy Greavu's Live Blog

Office 365 #SharePoint multi language custom form | Valy Greavu's Live Blog — Tue, 28 Jul 2015 21:41:56 GMT

Pingback from Office 365 #SharePoint multi language custom form | Valy Greavu's Live Blog

Localizing a SharePoint 2010 List Form with InfoPath | SharePoint Cipher

Localizing a SharePoint 2010 List Form with InfoPath | SharePoint Cipher — Fri, 24 Aug 2012 19:25:43 GMT

Pingback from Localizing a SharePoint 2010 List Form with InfoPath | SharePoint Cipher

Add Language Localization to a Form | Software Design

Add Language Localization to a Form | Software Design — Mon, 23 Jan 2012 16:59:06 GMT

Pingback from Add Language Localization to a Form | Software Design

re: Add Language Localization to a Form

nenemourinho — Mon, 21 Feb 2011 16:46:17 GMT

Dear Matt,

Using this method in InfoPath 2010 (Administrator -approved form Template) with MOSS 2010 I have a problem...

When I try to upload my template.xsn in the SharePoint Central Administration I have the following error :

Object reference not set to an instance of an object.

ConstructFromXsnFile failed with unhandled exception System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.InfoPath.Server.SolutionLifetime.Filters.<>c__DisplayClass2.<CreateDependentNodeList>b__0(BaseControl match) at System.Collections.Generic.List`1.Find(Predicate`1 match) at Microsoft.Office.InfoPath.Server.SolutionLifetime.Filters.CreateDependentNodeList.........

If I delete the calculated values the upload is ok.

Have you already try this method with 2010 environment ?

Thanks in advance

Reference URL | Abhi's Blog

Reference URL | Abhi's Blog — Tue, 08 Feb 2011 09:48:16 GMT

Pingback from Reference URL | Abhi's Blog

Multilanguage InfoPath Forms | Catalin Soca Blog

Multilanguage InfoPath Forms | Catalin Soca Blog — Wed, 19 Jan 2011 09:19:29 GMT

Pingback from Multilanguage InfoPath Forms | Catalin Soca Blog

re: Add Language Localization to a Form

rahulbabar — Sat, 30 Oct 2010 05:30:39 GMT

Very nice article! Can we get language in code behind rather user select it from the drop down menu?

re: Add Language Localization to a Form

pnewhook — Wed, 10 Mar 2010 18:05:08 GMT

Great article. I hope 2010 features more built in internationalization features.

As a time saver, instead of clicking throuh the dialogs in the "Add the expression boxes with data filtering" section, do it once then copy the xPath that's generated. You then only need to edit the Name parameter.

Multi-national(langage) support? | keyongtech

Multi-national(langage) support? | keyongtech — Thu, 22 Jan 2009 02:36:07 GMT

Pingback from Multi-national(langage) support? | keyongtech

Screen Tip translation in IFS | keyongtech

Screen Tip translation in IFS | keyongtech — Sun, 18 Jan 2009 16:58:10 GMT

Pingback from Screen Tip translation in IFS | keyongtech

re: Add Language Localization to a Form

jbaekken — Thu, 09 Oct 2008 08:57:48 GMT

Got the same problem as pnewhook with filters on dropdown boxes on browser-enabled forms. Did you find a way to solve this, engy?

re: Add Language Localization to a Form

pnewhook — Wed, 03 Sep 2008 16:24:52 GMT

I've got the problem engy mentioned above. I can't get localized dropdown boxes because filters are not supported in brower enabled forms. Does anyone know of a work around for this?

dropdownlist blank first row

dropdownlist blank first row — Thu, 15 May 2008 23:16:15 GMT

Pingback from dropdownlist blank first row

Localization in InfoPath form

SaurabhKV — Mon, 05 May 2008 19:33:27 GMT

A very good link to implement localization in an InfoPath form.

re: Add Language Localization to a Form

Hans Andringa — Mon, 14 Jan 2008 12:32:57 GMT

Happydigit,

I have also encountered the exact same problems as you have mentioned. I got a good solution/workaround for both problems.

For the first problem about working with large number of controls the solution is easy. The performance problem is caused by your browser rendering all the controls in JavaScript. The XPath query for each label is under water being translated into very large functions and arrays:

function _d(objContext,enumMode){

return

Expr.xpath_And(Expr.xpath_Eq(Expr.vpath_Select(objContext,[[[1,-1],[1,-1],[1,-1],[0,38]]]),"Title"),Expr.xpath_Eq(Expr.vpath_Select(objContext,[[[1,-1],[0,39]]]),Expr.vpath_Select(objContext,[[[1,-1],[1,-1],[1,-1],[1,-1],[1,-1],[0,16]]])))

}

When you change your language in the Drop-Down List Box, all the functions are being called in JavaScript and all the controls are being updated with XPath. If you have more than 10 controls, this will be very very slow.

The solution is easy. Just let the server change all the controls instead of the browser. So change your Drop-Down List Box to "Always" Postback. You can find this by double-clicking on the control and by going to the "Browser forms" tab in InfoPath 2007. I am not sure what your server load will do when multiple users are changing their language at the same time, but I assume this won't be a problem. Another good tip for boosting your performance, is to use multiple views.

For the second problem it's rather a workaround then a solution, because there is a bug in the Design Checker. When you update the XPath query in your control, the Design Checker doesn't sees that you have a WHERE clause in your query. It just thinks that you have selected a value from a Repeating Group (which is actually the case). You just cannot make an update to your control. The workaround I have found is when you want to change the XPath query, just remove the old control and add a new one. Then copy-paste the right XPath Query into it:

xdXDocument:GetDOM("Language Settings")/LocalSettings/Labels/Label/LocalLabel/@Value[../../@Name = "Title" and ../@Code = xdXDocument:get-DOM()/my:DTAControls/my:Global/my:Language]

Or you can just save and publish your InfoPath template and ignore the errors :p

Great topic btw!!

Greetings,

Hans