I have a larger graph that I've imported into D360 that takes upwards of five minutes to open composites and navigate my way thru the data flow. Within in LAE I could navigate thru all levels of the graph very quickly and easily with almost no delay (at most 1.5 second delay in opening the composites)
I've imported similar sized graphs into D360 and none have quite the same issues that this one does with GUI response time. Is there something server side that I can do to adjust the speed or perhaps change within the graph itself? I'd like to stay away from breaking the graph up into smaller components as much as possible because of how tightly integrated the processes are.
Hi Josh, I've create a support ticket for this issue.