Hi @webasylum
>> 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 ?
Correct, a publishable and localizable's super interfaces will look like:
<SuperInterfaces>
<SuperInterface type="Composite.Data.ProcessControlled.IPublishControlled,Composite" />
<SuperInterface type="Composite.Data.ProcessControlled.IProcessControlled,Composite" />
<SuperInterface type="Composite.Data.ProcessControlled.ILocalizedControlled,Composite" />
....
</SuperInterfaces>
>> 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.
does save not work in standard editing data workflow, or in your custom application? If you have a CustomUrlAction that shows the editor, you would have to pass information about current language to the frame
