Hi,
I have recently implemented an exposer table from a collector to be viewed off a topology card in an epm system. I have implemented this in several connectors already and have not received this DIS error before. I tried looking up the error code and couldn’t find details about it anywhere. Below in the image you can see the error code and that the page clearly exists above in the display tag. Anyone have any idea why this error is showing up? 
Hi all,
The fix was to add a standalone Param, for example a title header to organize the kpis. The validator should recommend this instead of saying the page does not exist as it can confuse the user since the page does indeed exist. In the future if anyone runs into this error just add a title header to organize the kpis and it will fix it.
Thanks,
Meekaeel
Hi Meekaeel,
The validator should ignore pages that start with “CPEIntegration_”.
A task was already created for that (ID 128947)
In short:
For EPM (CPE) integrations table column parameters can be displayed as standalone parameters by defining a page name that starts with “CPEIntegration_”.
This approach allows you to export specific parameters, similar to how it’s done for a DVE element.
The goal is to create pages like this:
For example, to add the Number Endpoints parameter to the UI, you can use the following configuration:
<Display>
<RTDisplay>true</RTDisplay>
<Positions>
<Position>
<Page>CPEIntegration_Data/Network</Page>
<Row>1</Row>
<Column>0</Column>
</Position>
</Positions>
</Display>
For more info what is CPEIntegration pages please see the following:
Topology app configuration | DataMiner Docs
Kind regards,
See my above comment to pedro, the fix was adding a standalone param IE (a title header). The validator has the wrong wording it should recommend a title not tell the user the page does not exist.
Hi Meekaeel,
This check basically does the following: It iterates over all parameters in the protocol and keeps track of the page name mentioned in the Position/Page (regular pages and page button page names). Then it iterates over all pages mentioned in the pageOrder attribute and verifies whehter each page mentioned in the pageOrder attribute (that is not a separator or web interface placeholder) is used somewhere in a Position/Page of a parameter.
The validator check will raise an issue if there is no parameter that is positioned on this page. Another example could be that RTDisplay is false for this parameter (but in this case another issue would be raised stating that RTDisplay was expected to be set to true for that parameter).
Do you have a parameter defined in your protocol that is positioned on this page? If so, can you provide the XML of that parameter?
The issue is that that page is used to expose data from a collector or a table to an EPM card. The fix to get rid of the validator error I found was to just use titles to organize the page, that causes the validator check to pass as they are standalone params. The error shouldn't get thrown on CPEIntegration_Data/entity pages, as most of the time it is columns off of a table getting exposed to an EPM card. The validator should recommend titles instead of saying the page doesn't exist.
The user should not be forced to add parameters/titles if they do not want to:
For me, the validator should ignore pages that start with "CPEIntegration_"
Kind regards,