Joining OEEH and ARSC

Nathan Manseau

Hello,
I've been in the process of migrating reports from our old SX and converting them into their modern equivalent in CSD / ION / Birst. Whether that be a Data View in the Data Fabric, or a Dataflow and Workflow in ION or a report in Birst.
However, I've run into an issue I'm hoping someone has the answer to.

In our existing SX which is a very old on premises version, we have a number of reports that seem to have JOINs between tables which Birst does not allow. Such as OEEH and ARSC. This does not make sense to me, as relating the header of an order (OEEH) for a given customer (ARSC) is bound to be necessary.
However, If I try to recreate for example, a report which includes ARSC.custno (Attribute) along with ARSC.periodbal_5 (Measure) and try to add say OEEH.orderno it refuses because theres no relation between the objects which there should be between custno and orderno at least, even with the addition of periodbal_5.

Does anyone know how to get through this or possibly join these tables together? I've tried to within Modeler → Relate but to no avail.

Tamas Molnar

Hi,

To join tables, it is needed to be on a different parent space, and package connect them on a new child space with complex joins.

The joins are not so flexible, A-B connection is easy, but A-B-C connections are tricky. A-C connection usually not strong, so it can loose the A-B and B-C join filtering feature, the report may be needs to be filtered again like the joins logic.