Hello,
the best way is either to use the aba or something in the wedge_address_config (which can be different for every FI) and then append this to the user_id. See the below for explanation on the first part.
In SDK versions of 2.164.0 and newer, hq_credentials is pulled from vault properly for multitenant extensions. So now you can just do self.hq_credentials.aba
Alternatively, you can use wedge_address_configs here: https://docs.q2developer.com/tutorials/online_banking/configuration.html
The way this works is every Financial Institution has their own database, and when the request comes through online banking heading for your extension HQ will go to a few tables and grab various bits of information. One of those bits that it grabs is the configuration table that is how the information comes through to the extension. So Wedge Address Configs are a per FI configuration. So you can do something like:
WEDGE_ADDRESS_CONFIGS = DbConfigList(
[
DbConfig('fiName', 'Insert FI Name')
]
)
Then when you do q2 install you can set what that value should be. Same thing when we install the extension into an FI environment, we would set that value when we install said extension. Then during your extension code you can do something like:
self.wedge_address_configs['fiName']
Hope this make sense, let me know if you need further explanation.
-Trey
@<1293619705470259200|Trey Teter> Also have a question about wedge address configs being a per fi configuration. If I define the wedge address configs in say extension.py does that mean I have to change 'insert Fi Name' everytime I install the extension into an FI environment to the proper Fi Name? Is there a way for the process to not be so manually intensive? Aba should be sufficient for my use case assuming it doesn't change overtime, I just want to better undretand wedge address configs.
DbConfig('fiName', 'Insert FI Name')