@brian.gummin - have you seen this before or have any ideas?
@Steve Hurst
I assume you checked all these values exist by exporting the mobile DB, if not export the mobile DB and run the below query to see whether the values are returned
SELECT m.message_text,c.code_value
FROM metrix_code_table c
JOIN mm_message_def_view m ON c.message_id = m.message_id
AND m.message_type = 'CODE'
WHERE c.code_name = 'MM_SCREEN_TYPE'
Also please note the translations are pulled from the view “mm_message_def_view”
I checked in my FSM 6.25, and it works fine and created few screens :)
@jevin.fernando - that pointed me in the right direction and helped solve the issue!
I had checked the metrix_code_table and the “Standard” record was present, however, using your script it showed that it was not present in the mm_message_def_view. The cause turned out to be that the customer had a cust_message_def record defined with a message_id of “STANDARD” and was therefore being excluded from the view and so did not appear on mobile!