Skip to main content

We have an extractor set-up, but had to manually input a table. Now, we can't call such table in the extractor's data connection schema because it is in a different scope (manual uploads require a global connection, hence the different scope ).

Hi,

you could write a transformation in Global Scope that is creating your table in different scope namespace.

 

E.g you have a table <YOUR_TABLE> in global scope.

You can use:

 

CREATE TABLE <%=DATASOURCE:YOUR_SCOPE%>."YOUR_TABLE" AS

(SELECT * FROM YOUR_TABLE);


Hi,

you could write a transformation in Global Scope that is creating your table in different scope namespace.

 

E.g you have a table <YOUR_TABLE> in global scope.

You can use:

 

CREATE TABLE <%=DATASOURCE:YOUR_SCOPE%>."YOUR_TABLE" AS

(SELECT * FROM YOUR_TABLE);

Thank you so much for replying!

 

I'm getting the error message "Execution error: Not allowed to access schema DATASOURCE:ABC_Extractor". Any idea on how to circumvent this?


i dont think you can call a table in Global schema from another scope(Target Scope). Instead create a view or table in the Target SCOPE by using this table in Global schema.


@muthappan.alaga is right, only the global scope can 'see' data from other scopes. It should be possible however to create new tables in other scopes in a Global Transformation, as explained here: How do I copy a table from one Data Connection to another? (celonis.com).

 

Next to that, during a manual upload, you should be able to specify the target scope, so you can upload it directly to the right place. See the 'Configure Upload' options as specified here: Uploading files (celonis.com)


Reply