the APEX api call, change the repository, in the context of the application has no effect

Hello

I call APEX api stored procedures manipulate the repository (such as apex_lang.update_translated_string, apex_lang.publish_application or apex_instance_admin.set_parameter) pl/sql by setting apex_util.set_security_group_id (< workspace_id >) following this example indicated in the documentation of the api of the APEX:

Start

--

-If running SQL * Plus, there set the environment

-for the workspace Application Express associated with this schema. The

-call to apex_util.set_security_group_id is not required if

-you are running as part of the Application Builder

- or an Application Express application.

--

C1 in (select workspace_id from apex_workspaces)

loop

apex_util.set_security_group_id (C1.workspace_id);

"exit";

end loop;

-Now, actually create the mapping of the language

apex_lang.update_translated_string (p_id = 123456789 >)

, p_language = > 'nl '.

p_string = > "says is a test");

commit;

end;

/

Call it the SQL guest (or Toad) everything works fine.

But when trying to call apex_lang.update_translated_string from an application (with or without the security_group_id) APEX, nothing happens. No error message, the process is complete, but the string in the filing of the translation has not changed. Same effect for other api call that I mentioned. I tried the different authentication scheme in my application: DB account, users of the APEX, custom.

An idea or a clue on what I'm missing here?

Kind regards

Christian

Dear Mr. Rokitta,

I tested myself on apex.oracle.com just now, and I had no problem using your anonymous PL/SQL block to update the chain of my filing of translation.  It worked successfully to these two SQL commands in SQL Workshop and also inside an APEX application running.  I also looked at the underlying code, and it's so simple - also long the security_group_id is set correctly, the specified ID is valid and the language code is the code of language of the APEX_APPLICATION_TRANS_REPOS chain, the update should go ahead.

If set you a test on apex.oracle.com case where this would have been does not work, I would be happy to take a look.

Merry Christmas.

Joel

Tags: Database

Similar Questions

Maybe you are looking for