We have cases where several developers work on different tabs of the same dxp file. This creates a challenge in combining the work afterwards. Especially if new document properties, IP scripts, calculated columns have been introduced, you more or less have to save each working copy as a separate dxp and then manually merge the delta back into the main dxp. Would be nice to have some merging capability as for code development.
EPAM (Spotfire partners) offers an Spotfire Version Control extension that allows to do this. https://solutionshub.epam.com/solution/epam-bi-version-control
looks like its been in future consideration from past 6.5 years.
Merging two dxp files with data connections, data transformation, pages, marking and visualizations would be very much helpful. This feature is there in many other software. lack of the this feature is creating a lot of trouble and limiting our ability to divide and develop reports.
We also frequently struggle with this limitation. Since one editor doesn't know, whether another editor is working on a specific template at the same time, it also occurs that they overwrite each others modifications. (Saving into separate dxps is due to the amount of changes in a short time too difficult.)
Hence, a simple indicator, whether anyone else with edit rights is using the template at the time would be very helpful.
We have the same situation described by the OP. We could assume user-created objects in each DXP would be uniquely named so there are no name collisions when bringing all objects together. A pop-up window could list any collisions. Analyst client could have a File/Import option to pull another dxp into the current one.
In Spotfire 6.5 and later it is possible to drag and drop visualizations and pages between two dxp files.