Jedox Ideas

Let us know how we can make Jedox even better!

Add a new idea Subscribe
Status Planned
Workspace Jedox Platform
Categories Integrator
Created by Guest
Created on Mar 18, 2025

RELATED IDEAS

automatically adapt namespace in external jobs when installing a model into another namespace

Situation:

You develop a model with several integrator projects.
Those projects are linked to each other by external jobs.

Unfortunatelly the namespace of the target project is quite hardcoded within the scope definition of the external job. (see picture)

e.g. if you have the namespace "Demo":

<job modified="1742307694869" name="J_ext_Groovy_Test1" type="ExternalJob" >
<project scope="Demo_de.assetcontroller.testnamespace">Test1</project>


Problem:

Imagine you install the model into another namespace "Test" instead of "Demo".
Then the namespace in the external job will not be changed automatically from "Demo" to "Test".

So the execution will fail.


We tried to use a workaround with variables. (see screenshot 2)
But this gets problems with the Integrator UI and probably is not really supported.
Also you have to change the variable manually.


Solution:

There should be a new standard setting within the external job
where you can set the namespace of the target project to a dynamic reference.
Something like: <namespace of current model>project_xyz

-> kind of relative reference, so that all projects within the same model can see each other
without using a hardcoded namespace

Thanks for evaluating this request :)
JL


etl_namespace_f...
etl_namespace_f...
etl_namespace_for_ext_jobs__2.png
Open full size
etl_namespace_for_ext_jobs.png
Open full size
etl_namespace_for_ext_jobs__2.png etl_namespace_for_ext_jobs.png
  • ADMIN RESPONSE
    Mar 21, 2025

    Thank you for your great idea. While we cannot commit to a specific target version, we will consider adding it to our future internal backlog. If you can add further information about the context of this feature, please add it here so we can evaluate it more fully.

  • Guest
    Jun 5, 2025

    The Scope of the Integrator should by default and always be the current namespace.

    Actually, having the possibility to execute something in a different namespace hampers the basic idea of using different namespaces to establish different environments.

    Reply
  • Guest
    May 30, 2025

    Using external jobs in combination with models is definitely necessary, and it should not require manual configuration. I believe the behavior regarding namespaces should align with how hyperlinks work in the report section where the namespace doesn’t need to be explicitly included in the hyperlink, but is still automatically tracked in the background. This ensures that only reports from that namespace are opened.

    Reply