We have an requirement where we need to filter the data from Global Code on the basis of a specific logic,To acheive that we have created a view ,But if we then use this view in lookups for different fields we see that message translations configured on Global codes stop working.
Is there a way by which we can still have message translations when we are using an custom view and not global codes directly
Hi
As per my knowledge, this limitation persists even if you create custom lookup screen and connect global code table itself. Translation works fine only in baseline lookup screens. I am not sure about latest release, but it was the case at least before UPD14.
Anyway, one solution could be, without creating a view, use few user_def fields on global code table to fulfill your filtering requirement. (Your problem may be complex than this),
BUT see if this would help.
Simple ex: if you want to show only a set of global code values based on task template
You may use, many user defs in global code for this. Only issue is, you have to create duplicate records for each criteria that you want to setup. But, translation would work, since we use global code table + the baseline lookup screen.
/Sanjeewa
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.