IFS Cloud 24R1 - How do you access IALs outside IFS for Data Warehouse/Data lake purposes

HI

What datamart/datalake have you set up?

Which profile did you use?

Jack

Hi ​@GaSoGB ,

IFS Cloud 21R1 deprecated the IAL Object Developer and IAL Configuration windows. It was released after 21R1, however it will still be accessible via the Aurena client. Other tools and features that employ direct SQL queries at the client layer, such as SQL data sources in Lobby and SQL statement type fast reports, will also progressively adjust to new methods of data access in addition to IAL Objects.

Because the new design does not recommend IAL objects that define SQL statements directly from the client application and deploy them as new objects into the database. OData RESTful APIs contain the backend database schema along with information about the database entities.

MOVING FORWARD

 

IAL objects are mainly used in quick reports, integrations to 3rd party systems, Lobbies, as a source for quick information sources and a few other purposes which are not in scope of this document. The above usages can be broadly classified into three main use cases described below. Each of these main use cases will be addressed and solved differently in the future.

1. The use of IAL objects to create a ‘named query’ that can be used later by a customer as a basis for quick reports, lobbies etc.

             • This will be addressed in the future with the introduction of a ‘Query Designer’ tool targeting                  non-technical users to self-service a ‘named query’ using our entity model as a base.

2. The use of IAL objects to present the underlying transactional data in a way that is optimized for BI, data warehousing and reporting purposes.

           • The existing Information Source framework can be used for this purpose. Defining                                    information sources is a developer task and will need developer tooling.

3. The use of IAL objects as one of several ways to provide self-service customization for customers instead of ordering a modification from IFS.

          • In the long term, there will be new tooling introduced to support self-service capabilities for                  lightweight customization. In the short term, this use case should be considered as a new                    customization requirement and therefore needs to be handled in IFS Developer Studio. It is                   recommended to create a new view in a customization project in IFS Developer Studio in order             to extract information from IFS Applications.

With IFS Cloud 21R1 every customer is expected to have a ‘Customer Solution Repository’ that stores all their customizations and configurations that they are responsible for. The Customer Solution Repository also enables a clear separation of the “as supported by IFS” and “as delivered to customers” aspects of a solution. Configuration and customization are the customers’ responsibility, regardless of whether they self-serve or buy a service from IFS consulting or from a partner to do the work. Most customers will achieve this by using the IFS Lifecycle Experience ‘Build Place’ as a service from IFS.

Thank you & Kind regards,
\ Krishantha