Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Incorporating a variable and for loop for churn reason #4

Open
2 of 4 tasks
fivetran-avinash opened this issue Oct 14, 2022 · 0 comments
Open
2 of 4 tasks
Labels
enhancement New feature or request

Comments

@fivetran-avinash
Copy link
Contributor

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

Churn reasons are currently mostly customized in our recurly__churn_analysis based on internal logic in the Recurly Churn API. https://docs.recurly.com/docs/churn-analysis

However, it's likely customers have their own internal churn logic that differs from Recurly. It makes sense for us to incorporate additional variables so you can customize exactly what churn looks like based on internal definitions, then implementing a for loop to complete the data.

Describe alternatives you've considered

One possible way to make the variable work is to leverage a dictionary, then use a key value pair for loop that would be able to provide you all the necessary logic to produce your own churn reasons!

Here's an example of a key value pair for loop in action: https://github.com/fivetran/dbt_salesforce_formula_utils/blob/main/macros/sfdc_formula_refactor.sql

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

No response

@fivetran-avinash fivetran-avinash added the enhancement New feature or request label Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant