I have a custom tree for a datatype where I changed the PK Guid to a PK Integer and have the console successfully listing it in the custom tree with Add/Edit actions.
The datatype was originally created using the datatype wizard with Localization switched on (Generating 5 language templates) and changed in line with recommendations in another thread (http://compositec1.codeplex.com/discussions/391830)
However, the resulting DynamicTypeForm and DataMetaData XML templates save the data records into the standard DataType published datastore - Ignoring the selected localization language setting of the console.
Question:
Am I correct in thinking that the appropriate \DataMetaData\~.xml file of the datatype needs some 'culture' settings within the <SuperInterfaces /> tag to enable the console to save the datarecord into the correct localization datastore ?
I've looked at both DataScope and SuperInterfaces (http://docs.composite.net/Data/Defining-Data-IData-types-in-C1-using-C/Super-interfaces#_Toc325357975) and can't work out how to implement 'ILocalizedControlled'
into the custom application so that it saves correctly.