We don't have a lot of details on Q2 Discover (we being the SDK devs), but it does look like this is what this does. You could probably get more information from your Q2 CEM.
I do believe that some FIs have used Google Tag Manager via UUX payload to also do this tracking.
I don't think this would cancel the entire recurring transaction. The API is using CancelGeneratedTransaction and not CancelRecurringTransaction. I would imagine that this would only cancel the instance and not the series.
We currently do not have Composable Dashboard enabled on the sandboxes. There is a way to test the look and feel of an extension on Composible Dashboard. Under Services in the sandbox there is a item called Content Block Preview" that will help develop for Composible Dashboard.
Hey Ethan,
We typically see the monkeypatch setattr implemented a little differently.
This is what you have:
monkeypatch.setattr(
"q2_sdk.hq.db.generated_transactions.GeneratedTransactions",
MockGeneratedTransactions,
)
But we would typically see a function and not a class.
The other approach you could take here is to use the mock_q2_request decorator and mock the data being returned from the calls.
You shouldn't need to add any headers. The coreflow doesn't directly interact with the network call that calls your core, that is done by Host Adapter down stream. The Bridge/Host Adapter should take care of that for you. Is there a specific reason you need a header, or are you seeing any failures in your testing that would lead to thinking a header is necessary?
Hello Matt,
Setting the timezone is going to depend on if this is going to be a single instance for a single FI.
If this is needed for a single FI, then staticly setting the timezone in the code is the simplest solution. Using the pytz library is typically how that is done, and you could set something in the db config if you wanted to changes this without deploying code.
If this is needed for multiple FIs which all could be in different timezones, the best solution is to make an HQ ...
Hey Tanner,
Make sure you are on the latest version of the SDK when you run q2 setup_db. This should work, but if you are still having issues, submit a ticket and we can dive into the database to see what is going on.
Thanks,
Paden Rose
Hey Ethan,
Tests can be added to a periodic job in the same way that they are included with extensions.
Since we use pytest in the SDK, all that is really needed in a file name that starts with "test". For example, if I run "q2 create_endpoint" and create a new endpoint name "addingTests" the SDK would build a new directory (on the latest SDK version) called addingTests and an entrypoint.py is also written with some templated code. To add tests to this, I would simply create a new dir...
The DateColumn class is an enum (enumeration) and is used to show the possible values in a descriptive way without needing to know what the actual values are. It is used a little differently than a typical python class. Instead of instanciating an object on the class, you use a dot to access the members in the class to pick which value you want.
Picking a create date column looks like this
date_column = DateColumn.CreateDate
You can ream more about enums [here](https://docs.python....
Currently, no, there is not a way to determine this. To remedy this, I'm going to add Principal and Interests columns to the return on the function you called out. Once that is done, checking if the total transaction amount matches the principal amount should tell you if it was a principal-only payment
Hey Eric,
Can you add a little more detail about what you are using? LookupUser, and the "Data" field you mentioned makes it seem like you are referring to Caliper API, and not Q2 Central. LookupUser in CaliperAPI does have a 10 user limit, and that is mostly because it is meant to be a very targeted call, and not used as a search function. But, if you are in an extension using Q2 Central, you should not have to call the CaliperAPI. Can you add a little more information about your code...