on 09-17-2008 10:15 PM
Even if we put only one language "English " on the repository
still we can turn Multilingual = YES on field level
What the use ? Anything behind the scenes?
-Sudhir
Edited by: Sudhir Reddy Maddulapally on Sep 17, 2008 11:15 PM
Hi Sudhir,
You can discard this as bug.
Until and unless the languages are defined in repository, the repository neither allow you to enter the names of fields in multiple languages and nor the data.
+ An
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the replies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sudhir,
You have to ignore this because there are many things in the current MDM versions in which even if you set the value of some property it will be of no use.
Example: In workflows if you set Active = No but still you can set the remaining properties like Autolaunch, Trigger Actions etc though they are of no use so these properties should be disabled.
Regards,
Jitesh Talreja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sudhir,
You are right in noticing this point that even though the repository is not multilingual the fields can still be set as multilingual.
I am not sure whether this is a bug as this feature of multilinguality for data and meta data has always been enabled in this manner .As per my understanding the repository needs to be set as multilingual with all the permissible languages selected in MDM console only then for every field in the repository that carries multilingual data,will the data be displayed in that particular language if not then all the data will appaer in the primary language it self in your case English.
It is more like you can set or reset the mulitilingual property for each fiel din the repository but it will come in effect only if teh Repository languages are set accordingly else not,so its more like an interdependent feature which can be enabled but works only if the other condition attached to it is True.
It's more or less the same as the case for Functions and Tables and fields tab for each Role in console although we can restrict the functions like ADD rec,Delete Rec under the functions tab but it will work effectively only when you have set the tables restriction as well accordingly for the same role ,so here again it is an interdependable action but allows you to set it independently.
Ideally it should not work independently if its a dependent action but this is the way MDM is designed and works .
Hope It Helped,
Thanks & Regards
Simona Pinto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.