Hi Johan,
Can you inspect the get_gui_transl_nav procedure in your IAM and SF database? Last time I check there was an exception built in to only allow NL translations to be returned.
Hi Mark,
Yes, Here it is and it seems correct:
1ALTER procedure [dbo].[get_gui_transl_nav]( @usr_id usr_id , @gui_appl_id id , @platform platform , @appl_lang_id appl_lang_id )asbegin
The debugging of this will probably take some effort. Last thing I can think of that the gui_transl_nav view may be altered. Could you double check that one too?
If that also looks okay, then I suggest creating a ticket for this.
Hi, I checked the view in IAM and TSF and they both have same definition. But what I also see is that I have different definition for this view in MOD database. Let me share both below:
TSF and IAM:
1create view [dbo].[gui_transl_nav]( "usr_id", "project_id", "project_vrs_id", "gui_appl_id", "platform", "appl_lang_id", "type_of_object", "transl_object_id", "transl_form", "transl_grid", "transl", "transl_plural", "tooltip_text", "help_text")as
MOD:
1create view [dbo].[gui_transl_nav]( "project_id", "project_vrs_id", "appl_lang_id", "type_of_object", "transl_object_id", "transl_form", "transl_grid", "transl", "transl_plural", "tooltip_text", "help_text")as
I don’t know if it helps but another thing that I found is that when I run the below script in IAM or TSF database then I see no results but when I run it on MOD database then it gives me correct result:
1select * from gui_transl_nav where project_vrs_id='7.0' and transl_object_id = 'projectbeheer'
Hi Johan,
The difference can be explained as the Software Factory and IAM have different model definitions. For example, IAM makes use of a table called transl whilst the SF uses transl_object_transl (2023.1).
I'm not sure what the MOD database is or what it's use is. But it seems to me there have been alterations to database objects therefor limiting the result and causing issues.
Again, I suggest creating a ticket for this. I feel that it would be necessary to rerun all scripts from the installation package (excluding 020_upgrade.sql). This will ensure that all objects are back to its original definition.