AdminSteve Brewer (Product Manager, Omatic)
My feedback
4 results found
-
0 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment The EveryAction API does not current support the retrieval of the custom fields on the Recurring Commitment. When this functionality becomes available in the EveryAction API then the connector can be updated to support this functionality.
-
72 votes
An error occurred while saving the comment Thank you for your idea Milly. We can definitely see how being able to save and then reuse a set of transformations across multiple formulas would ensure consistency and make it less likely that errors or data problems will occur.
-
2 votes
An error occurred while saving the comment Thanks for the feedback Christina.
Can you provide use cases for those scenarios so that we can understand which connectors, the type of data, etc would be driving the need for additional scheduling options. We want to be sure to understand the need behind these so that we can tackle in the appropriate manner as needing to run a formula at some other scheduled frequency could call out other business reasons that would need us to consider other areas of the product.
The EveryAction API does not current support the retrieval of the origin form field on the Contribution. When this functionality becomes available in the EveryAction API then the connector can be updated to support this functionality.
Note - the origin form field is the original form that the recurring commitment and first contribution was created from.