In Logi Info Studio, you create a report and add SQL queries that retrieve numeric event attributes from the operational data store. You then configure a Dashboard panel to display the custom report and deploy the custom Dashboard in

B2B Data Exchange

.

You cannot create custom Dashboard panels based on the following reports:

Unresolved Error Events by Partner (eventsbypartnerErrorRepository.lgx)
Unresolved Error Events by Account (eventsbyaccountErrorRepository.lgx)
Unresolved Error Events by Event Type (eventsbyeventstatusErrorRepository.lgx)
Unresolved Error Events by Event Status (eventsbyeventstatusErrorRepository.lgx)
Tasks (dxtasks.lgx)

When you create custom reports in Logi Info Studio, you can copy the SQL constants from the default Dashboard and modify them based on the KPIs that you want to display in the Dashboard panels.

You can use the SQL constants with the LogiXML constant token. When Logi Info Studio processes the custom reports, the constant token expands the SQL constants. For example, you use the following SQL query:

select facts.ACCOUNT_ID, sum(EVENT_COUNT) as SUM_COUNT from DX_ODS_EVENT_FACTS facts 
where @Constant.DX_ODS_FILTER_TIME_ORACLE~

The LogiXML constant token expands the SQL query to the following SQL query:

select facts.ACCOUNT_ID, sum(EVENT_COUNT) as SUM_COUNT from DX_ODS_EVENT_FACTS facts 
where to_timestamp(:requestDateBegin || :requestTimeBegin,'YYYY-MM-DD HH24:MI:SS') <= facts.TIMESLICE 
and facts.TIMESLICE <= to_timestamp(:requestDateEnd || :requestTimeEnd,'YYYY-MM-DD HH24:MI:SS')

If you create new parameters for your custom report, you must specify a unique name for each parameter. Otherwise, the Dashboard overrides the existing parameters with the same name or processes the parameter values incorrectly. If you create data layer links, you must specify a unique name for each data layer link in all of the reports. Otherwise, the Dashboard may display incorrect data in the Dashboard panel that you create, such as the wrong date or status.