unfortunately i don't know the right answer, but i would start to look at all existing APEX internal messages:
WHERE FLOW_ID = 4411
AND MESSAGE_LANGUAGE = 'en'
AND UPPER(MESSAGE_TEXT) LIKE 'ROW%'
Try to create Text Messages in your Application with the same name (and languages 'es'), maybe you get lucky and find the right one.
If you don't find the right message, it might be a bug.
Let me know what you find,
Spanish is a language that the Application Builder supports natively. It means that if you load this language, all the APEX engine internal messages will be translated into Spanish without any further work on your part. You can read more about it in the following:
I can't verify it now, but I believe that the text message you are referring to is called "ROW", and in your case it should be set to 'Fila %0'.
Thanks for your input Arie
You know funny enough I did change the "ROW" text message but to no avail, as for the language installed it does have the APEX spanish translation activated but we opted to go for the english one, as troubleshooting using the docs and forum help (such at this one ) it's a heck lot easier. I don't know if that mught cause the bug
Hello (Is Jivanvl your first name?)
>> I did change the "ROW" text message but to no avail
Let's take a step back. What you mean by changing the text message? You are not supposed to change the original – English – text message. You need to add a new text message, by the same name, under the 'es' language.
>> we opted to go for the english one, as troubleshooting using the docs and forum help (such at this one it's a heck lot easier.
Just so you know, even after loading extra languages, you can still work with English as the Application Builder language, and run the application in any other chosen language(s). The advantage of loading the natively supported languages is that the very tedious work of translating all the APEX engine internal messages are saved.