Ok I will try do clear things up.
In arcmap, we have a layer with datadriven page unable to cleanup annotation for each page of our series.
So, for example, we do a project with a view (map) with all the same data (layers).
(In time it was easy with arcview 3 because the relationship of one dataset to many layout ; template in arcmap was painful but still one dataset and many template).0
Since a long time, with the end of templates, we had to change everything AGAIN can have as many mxd than layout needed (up to more than 100 in some projects).
With the introduction of datadriven pages, to improve annotation between pages, we generate annotation in datadriven pages. Now, we make the first layout, generated the datadriven annotation and, frustratingly, we duplicate this mxd for all the layout we need then adjusting each layout accordingly to our need with the view referring to the datadriven page. So, c1.mxd refer to the datadriven page 1, c2.mxd refer to datadreven page 2 and so on except where you have more than one view in one layout since the datadriven is stupidely links to the layout not the view. There we datadriven one and not the second which makes duplicated annotation.
When opening an mxd, except some time where it's bugging, the c1.mxd stay link to the datadriven page 1 (page ID) and c2.mxd stay link to datadriven page 2 etc. for as many layout we have with the same dataset. No question asks it's working fine except if you make a change in the dataset you have to open each mxd to correct it.
So now return in Pro. Yes Pro return to the nice one dataset many layouts with a plus, datadriven page oups, map series. So if we need to change something in the layers, only one project to open and correct not a lot (reducing the risk of error).
So, we start to parse small project from mxd to Pro to see if its good for production. We have to wait for 2.4 since cartography tools were not there. The export bug, the last stop to make useful Pro find a workaround with print via pdf creator waiting for a more straightforward Adobe solution.
So, like I describe in the beginning, in a 2 mxd projects, each one link the layout to the datadriven page it was save on.
In importing my two mxd, I just point to one Map and discard the second since it's the same dataset but two pages overlapping and with page ID defined in the field "carte".
The first thing I found is that, not like in mxd where the datadriven page stay link with the mxd, I have, each time I change my layout, have to manually go to the map series tab and redo navigate to. It's not straifoward and very time consuming. Why not make the layout referring to page 2 of the map series, like in mxd, stay on the extend of the series page it was made for. I try to find a checkbox or other parameter to do so. (By the way, like I suggest in Idea, why not link map series in map not layout since you can have many maps in one layout.)
The most frustrating thing I found was in editing my annotations. The first pass was made in map but, the finishing touch has to be made in layout for unplace or move some annotations hide by some layout element. Then, in this case, it was a nightmare. Doing this last cleanup can take about 1 hour or less by page but, in Pro, take more than a day. Why, because, at each change, the redraw doesn't work. I have to get out the activated map to return to layout and again, and again, and again make the page navigate to the good page in the series.
