Hi ​@Ed22 

You can do as follows.  let’s assume your main view is

inventory_part_in_stock.

in the where clause section you can do the following as example (it is just for illustration purpose only)

 part_no in (select co.part_no from  

 customer_order_line  co where  inventory_part_in_stock.part_no = co.part_no  ) and part_no exists in (select 1 from    purchase_order_lines PO  where inventory_part_in_stock.part_no = PO.part_no  ) 

If it solves your problem please like it

I used INNER JOIN and it works good. Can I also used it in lobby designer or in lobbies is allowed only one view?

​@Ed22 Please refer below post.

hi ​@Ed22 

The above example can be used in Lobby data source development. 

Hi ​@BawTrishM 

I think IFS latest cloud versions are depreciating the IAL usage. The example i gave is for lobby data source for joining different views. 

One more way of solving multiple views issue is  to give the view name as DUAL in the data source view section and in the column level you can have a SELECT statement and fetch that one value for each column from multiple views using joins. 

Please be careful with lobbies, as complex queries and joins may deteriorate the performance of the whole system.

The actual BI separates this load to an external resource - an SQL server or Azure resources.

Try using Query Designer to make your join. It makes a projection with the right columns. Use that projection for your lobby data sources. IAL is too much, as all IALs need to be filled with data at regular intervals of time, and you might show stale data if not configured properly. IFS can’t deprecate IALs without stopping half of the ad-hoc reporting. 

Solution Manager > Configuration > Query Designer > Queries