Views in the Staging database

Views are stored queries that can be queried in the same way as tables. In Infor d/EPM, you can use views in load queries, mappings, relational Application Engine processes, and in relational reports. Queries, on views that target an Infor cloud source, are parsed against a list of safe SQL constructs. In relational modeling, views can be created on the Staging database. System views are hidden.

Views are editable or read-only, depending on how they are created. Views that are created in SQL Management Studio, for example, or which are imported as part of a solution accelerator, are read-only in relational modeling.

View meta data and the views on the SQL database are separate objects, which can have these effects in these scenarios:

Placeholder views: A view is created in relational modeling but deleted in SQL Management Studio.; If tables or views that the OLAP model requires are missing from the target Staging database, placeholder tables are created and highlighted by a warning icon. You can delete placeholder tables or click Define View or Table on the Schema tab of the table and select Define Table Schema, or Define View as appropriate.; This scenario can also occur during import of an OLAP model, if element or fact tables that the model requires are missing.
View exists only in SQL: A view that is created in the SQL database is shown in the object browser for staging and custom data connections. It is shown in the in Views node of the Relational Modeling dashboard navigation.
View created by solution accelerator import: A view that is created by importing a solution accelerator (*trustedSQL) is read-only. It cannot be exported or imported with bundles. It is visible in the Relational Modeling dashboard navigation and in the object browser.
Duplicate names: You cannot create a view with the same name as an existing view in the SQL database.