Support choosing which collective member is the data source

Idea created by nanderson Employee on Nov 1, 2018
    Originally posted on UserVoice

    When configuring the PI System Connector, there is currently no option to constrain the communications for the data source of PI Tag data to a secondary or tertiary PI Collective member. 

    The ability to force the PI System Connector to use the secondary or tertiary PDA as the data source will allow customers worried about impacting their primary archive's performance to manually balance the load on their collective and eliminate impacting the performance of their existing solutions.