Hi @richardray can you please describe the use case you are trying to achieve? Although project/instance variables cannot be added to joins, it is possible to add custom conditions to conditional lookups which are based on project/instance variables

Hi @richardray did the workaround resolve your issue? Please let me know the use case you are trying to achieve

Hi @Christian Hauggaard , apologies for the delay in responding. 

My use case is that I have a project variable which I update during mock loads for a data migration project. One of the lookups uses a columnar join and a fixed join which is the mock load code. Rather than have a fixed value I was hoping to use the project variable.

Would the instance variable work in the same way?

@richardray yes the instance and project variables work the same way. The instance variable is for the new cloud-enabled version of TimeXtender (and only relates to an instance) and the project variable is for legacy versions of the application (e.g the version you are using 20.10.36 and relates to a project). Are you using ODX or Business Unit? 

@richardray 

I agree it would be a nice feature to have.

In the interim, I guess you could add an additional field to the table. The field would have a custom transformation, the project/instance variable. You would then have a field join instead of a fixed join. What do you think?

Hi @Christian Hauggaard, we’re using Business Unit.

I think for now, I will use @Søren Sørensen’s suggestion as that will work perfectly.

Thanks to both of you