Without knowing the details of your AF Hierarchy I suspect you are trying to get ProcessBook to do what can be better accomplished in an AF database. I have two thoughts for you. 1) If for example you are trying to view a variety of assets that utilize the same template, but are located in disparate branches of the element tree, you can search for those in your element relative dialog boxes in ProcessBook by searching for elements built using that template. This compiles a good list to scroll through. This will allow the multi-state conditions to remain static across all the elements. 2) In PI System explorer you can create a "Displays" node in your element tree and copy the target elements and paste them as references in that node and then they will all be available in one node for searching in ProcessBook. Again the multi-state conditions will remain static across the diverse set of elements.
A PI ProcessBook learning playlist can be found here: PI ProcessBook - YouTube
We also faced the similar issue before, we had issue with AF2 data reference in Multistate. You need to save your displays as.SVG and need to manually find the old path and replace it with new path.
I request to refer the below post How to keep multi-state intact in processbook when switching AF servers and DB? for more details.