cancel
Showing results for 
Search instead for 
Did you mean: 

PaPM - Analyze: Value Flow not showing

former_member845130
Discoverer
0 Kudos
961

Dear Experts,

we currently have an issue with the value flow diagram of PaPM´s analyze functionality. When we try to display the value flow diagram, the screen stays empty:

Clicking on any of the links ("Full Screen", "Settings") or dropdowns on the right part of the screen has no effect. PaPM does not display any error messages.

When we switch to data grid or chart, the diagrams are displayed correctly, only the value flow is not working:

Has anyone seen this issue before? Do you know if this is an issue with PaPM or maybe some specific browser settings?

We have already checked the following points:

- The run of the function that is analyzed was completed without errors.The data is correct.
- we added the URL to a list of safe sites in the browser settings in case any content display is blocked by the browser. This made the links ("Full Screen", "Settings") and dropdowns appear in the right part of the screen (First screenshot). Before that, the display was completely empty.
- The issue is the same in all browsers that we tested (Edge, Chrome, Firefox and Internet Explorer)
- We applied filters to the result data to make sure that there are not too many records. The example from the screenshots has 26 lines.
- The issue is the same in different function types (e.g. Join, Allocation,...) and across different environments.

We recently upgraded PaPM to SP20

Thanks

Michael

View Entire Topic
denvi
Explorer
0 Kudos

Hi krake ,

As an idea, try to check error messages in the browser Development tools (Ctrl+Shift+I in Chrome). It might be that required web service is Inactive in SICF.

Best regards, Denis

former_member845130
Discoverer
0 Kudos

Hi denvi ,

thank you for your reply. The development tools show this error:

"Uncaught SyntaxError: Unexpected token '<' (at d3.3.4.12.min.js:1:1)"

This is a screenshot of the code that shows the error at the first line.

This error message is the same in Chrome and Edge.

Is this something we can fix on our end?