- There's actually 2 things in place here for rights. There's a Property in the UserPropertyData table called StatementImage that must be True for the Customer. Also it must be True for the Account in question. This will often depend on the environment and whether it supports statement images via an adapter or not.
- You are spot on for OnlineBanking. There's other options such as 'Voice', and they exist in the Q2_UiSource table, but basically you always want OnlineBanking. In terms of the...
I think this is doable depending on which information you're looking for. There's a bit of complication in the details here, so I'd like to further understand the problem. Given an account Id that you've gathered through other means you are looking for what additional info? Transaction history, HADE values, rights?
Hi Mitul,
You are right, the create_online_user and add_new_account are the best solutions we have at the moment. We talked this morning internally about building a "clone_user" type of functionality. Is that more in line with what you are looking for? We want to make sure we're building for a use case that makes sense for you.
Brian
This has been released in 2.124.0 (https://docs.q2developer.com/change_logs/sdk/CHANGELOG.html#v2-124-0-2022-03-17)
Roy,
Great job discovering that install step! It's not often used, so it's possible we haven't seen it used by an external dev before on a local install and there's a bug. I'm guessing this is installed on your machine, either using WSL or a linux host since I don't see that path on the shared dev machine? With that information we can try to reproduce and patch it.
Brian
Nice question, Justin!
I think we are going to go the route of supporting WSL as well for this. Setting all the environment variables is a challenge, but sounds like you are well on your way on that front. Regarding cache, you will likely need to run memcached directly on the box. Until we get a helper for it, you may try this:
sudo apt install memcached
memcached -d
Swarup is right. The docker rm is necessary for now until we push a fix to the powershell script. The issue is only present with the combination of docker + powershell + pycharm.