Hi Todd,
It depends. If you are using the build_base_query for a repgen/poweron (https://code.q2developer.com/Q2Antilles/q2-sdk/-/blob/develop/cores/q2_cores/Symitar/core.py?ref_type=heads#L35) request you’ll be able to set the USE_SYMXCHANGE parameter it will then generate a SymXchange SOAP request instead of a SymConnect request. This would only be done with repgen/poweron objects; if you’re building a TR or IQ request it would not be converted and break once you switch over to SymXchange.
I would start planning for the conversion and compile a list of requests your implementation uses today. There is a new core available just for SymXchange at https://code.q2developer.com/Q2Antilles/q2-sdk/-/tree/develop/cores/q2_cores/SymXchange. This has several helpers to construct SymXchange SOAP requests beyond repgen/poweron.
When I asked in a call recently. It sounds like it is transparent to us. When the SymXchange is created you will need to add all the privileges needed, and also the repgens ran in the Symxchange Common parameters.
When I asked in a call recently. It sounds like it is transparent to us. When the SymXchange is created you will need to add all the privileges needed, and also the repgens ran in the Symxchange Common parameters.
— Josh Marshall 3 years ago