Passing stream results into a secondary stream's API path

I have three streams.

|=statement list

A field from accounts is used to populate the path for statement list. Two fields from statement list are needed to populate the path for statements.

I have the first two streams working the way I want by defining a class-specific stream slice.

class AccountRelatedStream(ParentClassStream, ABC):    
    def stream_slices(
        self, sync_mode: SyncMode, cursor_field: List[str] = None, stream_state: Mapping[str, Any] = None
    ) -> Iterable[Optional[Mapping[str, Any]]]:
        accounts_stream = Accounts(authenticator=self.authenticator)
        for record in accounts_stream.read_records(sync_mode=SyncMode.full_refresh):
            yield {"account_id": record["account"]["account_id"]}

I thought I could do something similar for the last stream, but this isn’t working.

class StatementRelatedStream(ParentClassStream, ABC):    
    def stream_slices(
        self, sync_mode: SyncMode, cursor_field: List[str] = None, stream_state: Mapping[str, Any] = None
    ) -> Iterable[Optional[Mapping[str, Any]]]:
        statements_stream = StatementsList(authenticator=self.authenticator)
        for record in statements_stream.read_records(sync_mode=SyncMode.full_refresh):
            yield {"account_id": record["account_id"],"statement_id":record["statement_id"]}

I get an TypeError: 'NoneType' object is not subscriptable error. Any ideas?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Hey is this a custom connector? If so can you share the cdk version for it?

Hey @harshith – it is a custom connector. I’m on CDK version 0.1.56.

Got it. It will be helpful if you can share the repo URL so that we can take a look at the code. Is it possible?

Sure thing, here it is. source-canopy is the custom connector.

Hey could you also share the screenshot of the error? Or copy the complete error log here